Two design flaws for the price of one!
-
- This is another issue with the Discourse team not understanding that people using Middle Click/Ctrl + Click/Shift + Click/Right Click + Open in New Window/Right Click + Open in New Tab/anything else that opens a link outside of the current window
- This was caused by me opening the New topics in a new tab. The "New (4)" header was updated to "New (1)", but the topic list wasn't updated. You'd think that any competent developer would wrap the code to update both in the same place, so they stay in sync.
Bonus WTF for blakey: quote the source of this post.
-
Huh. This was fixed a couple weeks ago. (I know because I reported it on meta.d and verified the fix) Regression!
-
I had one a couple of weeks ago that I took a screenshot of but did not post where it said "Unread(47)" and below that said "No unread posts".
-
You'd think that any competent developer would wrap the code to update both in the same place, so they stay in sync.
They don't seem to update the actual topic list at all ever unless there is a new post in a topic, at which point they just tack it onto the top.
-
That would make Too Much Sense™
-
Although it's bad form to quote oneself, might I mention this...
@tufty said:I would also suggest that no PR ever be accepted if it doesn't have a fucking regression test.
Manwhile, objeffecationTwo gems in there. One's a jeffecation…
One thing that continually frustrates me when working with dedicated test teams is that, well, they find too many bugs.
… and the other is quote from http://software.ericsink.com/articles/Four_Questions.html
Don't we all start out with the belief that software only gets better as we work on it? The fact that we need regression testing is somehow like evidence that there is something wrong with the world. After all, it's not like anybody on our team is intentionally creating new bugs. We're just trying to make sure our product gets better every day, and yet, somewhere between 3.1.2 and 3.1.3, we made it worse.
But that's just the way it is. Every code change is a risk. A development cycle that doesn't recognize this will churn indefinitely and never create a shippable product.
(emphasis mine)
-
Also, another bug dicsovered.
I just edited the post above to add the emphasis, and committed. I then ninja'ed "jeffication" to "jeffecation", because it looks funnier. I also missed "manwhile", but I'm only on coffee #1
So, post as displayed :
And the edit as displayed by clicking on the "edit pencil"
Amusing, "non"?
-
Also, days since Discourse bug discovered: 0
-
They don't seem to update the actual topic list at all ever unless there is a new post in a topic, at which point they just tack it onto the top.
It's a good thing. The last thing I want if for the topic list to change on me as I'm about to click a topic.
-
Just hard-code the “0”. Saves time and remains accurate!
-
It's a good thing. The last thing I want if for the topic list to change on me as I'm about to click a topic.
Except it happens to me pretty much every time I make a post, just as I go to click on the next topic... fuuuu the list has changed.
-
The last thing I want if for the topic list to change on me as I'm about to click a topic.
I get this all the time in the suggested topics at the bottom, though.
-
You just did it to me you belgian.
-
How very dare you, I am British, not B*****n.
-
Europese.
-
-
Hedging my bets.
-
Ah but there's a difference. Being European isn't a critical offence but mentioning the B word around here... is.
-
Regression!
Well, this is version 1.0. Of course it is different from previous versions!
-
Two gems in there. One's a jeffication…
One thing that continually frustrates me when working with dedicated test teams is that, well, they find too many bugs.
Yes, I can see how frustrating that would be. I have written the perfect software, 1,000,000 lines of sheer beauty, and along comes a test team that has the nerve to find bugs in it??? Sack'em! Sack'em all!!!
-
You'd think that any competent developer would wrap the code to update both in the same place, so they stay in sync.
You'd think, but considering the Unread counter doesn't get reset to 0 when you click 'Dismiss Posts', and it's been off by 2 for me on 2 different computers for me despite hard refreshes on both, I'm not sure we're dealing with that sort of developer.
-
Being European isn't a critical offence but mentioning the B word around here... is.
That's what we want you to believe.
-
You'd think, but considering the Unread counter doesn't get reset to 0 when you click 'Dismiss Posts', and it's been off by 2 for me on 2 different computers for me despite hard refreshes on both, I'm not sure we're dealing with that sort of developer.
To be fair, Jeff isn't really a main developer. He just directs the main devs in random and contradictory directions and signs the checks.
-
Jeff isn't really a main developer.
Yeah, I wasn't necessarily talking about Jeff.
They all use Discourse, I don't get why they don't see completely silly (and IMO easily avoidable) issues like these and just fix them.
-
It's a good thing. The last thing I want if for the topic list to change on me as I'm about to click a topic.
That happens all the time on the main topic listing page. I'll open it, then it'll jump to show topics that have just been updated. Usually as I'm about to click on a topic, so I end up clicking on the wrong one.
-
This has never happened to me on the main topics list. On the suggested topics at the bottom of a thread, as a new post comes up, sure.
But on the main topics lists I just get a blue banner saying there were changes; which I assume will push the topic titles down and away from your cursor, but I've never had this happen to me personally. But said banner only comes up once and is relatively short, while new posts can do any amount of displacement at any time.
Incidently, I like the parenthesized number of updates on the tab's title when on a topics list, but I'd rather much have it say the number of new notifications.
-
That happens all the time on the main topic listing page. I'll open it, then it'll jump to show topics that have just been updated. Usually as I'm about to click on a topic, so I end up clicking on the wrong one.
Happens to me at least 50% of the time on the main topic list. It's pretty frustrating and I even opened a Meta topic for it.
https://meta.discourse.org/t/dedicated-layout-space-for-the-blue-bar/19435
Then Jeff made a response about fixing UI items moving around by making UI items move around differently.
https://meta.discourse.org/t/dedicated-layout-space-for-the-blue-bar/19435/3?u=mott555
https://meta.discourse.org/t/dedicated-layout-space-for-the-blue-bar/19435/7?u=mott555
-
This has never happened to me on the main topics list. On the suggested topics at the bottom of a thread, as a new post comes up, sure.
But on the main topics lists I just get a blue banner saying there were changes; which I assume will push the topic titles down and away from your cursor, but I've never had this happen to me personally. But said banner only comes up once and is relatively short, while new posts can do any amount of displacement at any time.
Incidently, I like the parenthesized number of updates on the tab's title when on a topics list, but I'd rather much have it say the number of new notifications.
Yeah, it's just the blue announcement banner, but it does often pop up while I'm about to click a topic below.
@eviltrout, since it never gets to be larger than the one message, why not have a placeholder when the message isn't there so that they topic list doesn't move?
This reminds me of elements on a page that are visible at first, then hidden on page load.
-
Yay Markdown bugs/errors/design flaws that won't be fixed because it's technically Doing It Right.
-
@eviltrout, since it never gets to be larger than the one message, why not have a placeholder when the message isn't there so that they topic list doesn't move?
I think this has already been reported and acknowledged. I'll check out what's going on with it.
-
I think this has already been reported and acknowledged. I'll check out what's going on with it.
@mott555 reported it on meta.d, as linked above my comment, so it looks like it's reported already there.
-
They don't seem to update the actual topic list at all ever unless there is a new post in a topic, at which point they just tack it onto the top.
fun fact: suggested topics will auto-update
I just edited the post above to add the emphasis, and committed. I then ninja'ed "jeffication" to "jeffecation", because it looks funnier. I also missed "manwhile", but I'm only on coffee #1
This is a bug that I introduced by putting critical code inside of a transaction. I included too much on accident. Fixing commit.
-
fun fact: suggested topics will auto-update
AND -- get this -- the server-side code for this is SHARED with
/latest!¯\(°_o)/¯
-
fun fact: suggested topics will auto-update
fun fact: it doesn't update enough to be useful that it updates at all. if anything, it's more confusing than helpful because it's always so out-of-date with what I've actually viewed that I just ignore it entirely.
-
By the choices made about updating the UI, it's hard to believe that Jeff has ever even heard of tabbed browsing. It's like a random smattering of
- UPDATE IMMEDIATELY
- NEVER UPDATE
- UPDATE SOMETIMES
- UPDATE THIS BUT NOT THE OTHER
It's been months and I still get confused by topics and/or notifications being marked unread in certain places that I could have swore I just read and oh it turns out I really did read it just that this panel did not update or did update but randomly so long ago that the update is irrelevant but changed the number so as to make me notice it is different than it was and think it might mean something.
Filed Under: Must run on everything into WALL OF TEXT to prevent markdown from dicking up my posts thx2markdownrequiresnewlineorjustenoughspacing bugs.
-
I must be an idiot for every time I see the notifications button and open it to see that the notification is about something I already have open in another tab, so I switch to that tab to see what the notification was about, rather than lose my place in my current tab or opening a 2nd tab with the same topic in it.
Then, I see that the tab I switched to has now just received a new notification too, so I click it to see... SAME NOTIFICATION JUST SAW.
-
My about page has you covered.
-
Clicking your avatar made my Firefox hang. Congratulations.
-
Clicking your avatar made my Firefox hang. Congratulations.
Your post made me click on @Matches avatar. I just restarted my Firefox. Congratulations.
-
I'm afraid but also very, very curious now...
-
-
-
Yes, that's what others told me before.
BUT THEY LIED.
-
I'm afraid but also very, very curious now...
@faoileag said:It doesn't hurt.
@Arantor said:Yes, that's what others told me before.
BUT THEY LIED.
Ok... then... clicking on @Matches avatar will cause you severe pain, as electric discharge hits your fingertips, your screen will start flashing a shamrock and once the fog has reached your house, a long dead pirate will break the front door with an axe.
-
-
I can add that in an hour or two.
-
Yes yes, but how the fuck do you manage to crash a browser with an avatar?!
-
The
same way as with <kbd> tags?
-
How many copies of the first Frozen image do you have in your profile?
Filed under: I gave up trying to scroll past them, I don't know why they let you put so much text in your profile, didn't crash mobile Chrome either
-
Clicking your avatar made my Firefox hang. Congratulations.
And my IE11 tab; although, the recover tab button made it relatively painless.
Not All Bugs Are Worth Fixing
