Genuinely Useful Bug Reports
-
Go to the unread tab, then click dismiss unread button at the bottom. See this topic for a screenshot.
-
I moved 2 posts to an existing topic: Genuinely Useful Mobile Bug Reports
-
I moved a post to an existing topic: Topic progress bar incorrect, out of sync, or posts not loading
-
Bug: topics created by moving posts do not respect my setting to always watch topics when I enter them.
I noticed that too. It's not critical — I can easily fix it on a per topic basis — but it's really irritating.
-
I can easily fix it on a per topic basis
It's pretty easy to fix if one topic is spun off, though slightly annoying. Not so easy if nearly a dozen are.
-
Not so easy if nearly a dozen are.
It scales linearly with the number of topics, so it's not that hard. Just boring and annoying when the computer could take on the O(N) task for me.
-
Are you guys reading the post literally right above where you're posting? Because it has the solution to what you're talking about.
-
What I'm talking about is @ben_lubar's bug that topics spun off of a topic he is watching aren't automatically watched, which @dkf quoted.
Which, no, is not at all related to your workaround for another bug/option people can take if they don't care about legit replies to topics they're watching.
-
Bug: Categories Select box displays a scrollbar, even though page layout made scrolling in this drop-down impossible (at least with the number of categories defined by DailyWTF).
Fixed via:
BUGFIX: overflow auto makes more sense here. · discourse/discourse@e7c6a51
A platform for community discussion. Free, open, simple. - BUGFIX: overflow auto makes more sense here. · discourse/discourse@e7c6a51
-
I moved a post to a new topic: Times in user activity are way off
-
I moved a post to a new topic: Highlighting the incorrect topic in the topic list
-
I moved a post to a new topic: Nested quote expansion is broken
-
Since the browsers search feature is just not going to work properly with Discourse infinite scrolling(tm) I disabled it, and simply open the search box.
Next up we need to improve our built in search.
-
This is such an annoying chrome bug.
https://meta.discourse.org/t/chrome-keyboard-navigation-bug-in-compose-form/1611?u=codinghorror
Still broken about a year after I reported it.
-
I moved 17 posts to a new topic: Why can't I move deleted posts to a new topic?
-
I moved a post to an existing topic: Genuinely Useful Mobile Bug Reports
-
I moved 7 posts to an existing topic: Why does the URL change as I scroll through a topic?
-
I moved 2 posts to an existing topic: Feature suggestions for Discourse
-
This post is deleted!
-
[b]Bug:[/b] Discourse hijacks Ctrl+F
[b]Expected:[/b] Discourse leaves browser keyboard shortcuts the fuck alone
[b]Actual:[/b] As per bugFirst rule of web UI design: don't fuck with browser default behaviour, ever, under any circumstance. You guys created this infinite scrolling monster, you find elegant ways of making it work with web browsers. Hijacking Ctrl+F to sidestep this problem isn't elegant in any way shape or form, in fact it's probably the dirtiest, sloppiest, laziest hack I can think of.
Do not. Fuck with. My browser keyboard shortcuts.
-
-
I moved 6 posts to a new topic: How about a longer line length in posts?
-
Did you use Dismiss Unread button there?
-
Did you use Dismiss Unread button there?
No. As best I can recall the sequence of events following that, by the time I finished posting (in another window), AJAX had updated that to add a "one new topic. click to read" message, and changed the "Unread (5)" to "Unread (4)". I used the browser's back button to return to the Latest list. I can't remember what it showed, but I refreshed it, and it correctly showed nothing unread.
-
First rule of web UI design: don't fuck with browser default behaviour, ever, under any circumstance.
I can only like his post once, so I am replying to add another post I can like. Do not fuck with browser shortcuts.
Edit: What the fuck? I can't like my own messages?
-
-
In other news, search within topic now sucks a lot less.
-
In other news, search within topic now sucks a lot less.
Still fails horribly in high contrast mode.
-
Editor bugs:
Pressing Ctrl+V does weird things - in the previous post I was writing, it deleted everything from ^ to the end of line.Clicking in the editor when it doesn't have focus scrolls it a random amount up, and places the cursor away from where you clicked.
-
I've noticed some weird things with the editor as well - haven't had the energy to construct some repeatable steps for a repro though.
Think of it as the replacement for Backspace deletes two chars perhaps?
-
Think of it as the replacement for <kbd>Backspace</kbd> deletes two chars perhaps?
I was under the impression that Discourse was intended to be better than what it replaced. Better implies the exact opposite of "has similar bugs".
-
A thread about bugs in a piece of software, demonstrates a bug in the same software. Irony levels exceeding critical parameters...
-
A thread about bugs in a piece of software, demonstrates a bug in the same software. Irony levels exceeding critical parameters...
I was under the impression that they had fixed that particular bug ...
-
I was under the impression that they had fixed that particular bug ...
HOW I MERGE THE SOURCE CODES WITHOUT LOSE CHANGES?
-
Did you see 459 of 76 in the progress bar on this topic after posting the reply in the screenshot? You'll notice from the URL (or the share link) that this is technically post #463. cc @sam
-
I can make that happen with END, too.
-
Bug: clicking on the "in reply to" link does nothing
I did notice that on a post where the reply was the next post down, clicking the "in reply to" link would cause all of that prior post's quoted texts to expand. No idea what that was supposed to do.Expected: clicking on the "in reply to" link does... something? I expected to be taken to the original post, or have the original post be shown under where I clicked.
Chrome 33.0.1750.154 m (can't update from behind office firewalls without a decree from god, unfortunately)
Edit - wait, I've figured it out. Clicked a bunch more of them, and apparently it will show the previous post above the post you're looking at. But it doesn't move my infiniscroll bar at all. If the post I was reading is at the top of my page it looks like nothing at all happens (which it usually is, because I use the top of the page as my this is what line/post I'm on marker in case I get called away from it).
-
Bug: clicking on the "in reply to" link does nothing
Repro'd. Post concerned is here: http://what.thedailywtf.com/t/genuinely-useful-bug-reports/296/389
Chrome 34 and FF 32.
-
@codinghorror: I was able to repro with end as well.
-
That's because the in-reply-to post was deleted or moved.
-
BugGlitchFeature requestMild annoyanceWhatever:Left-clicking on both the avatar and the username works the same, bringing up the info panel.
Middle-clicking on an avatar brings you to user's profile, but middle-clicking on username brings you to current thread.
-
That's because the in-reply-to post was deleted or moved.
The correct behaviour would be to display an error message (if the post was deleted), or go to the post's new location (if it was moved). Just doing nothing doesn't make sense.
-
How many bugs are displayed in this single image?
-
I count 3. I suspect there are more.
-
How many bugs are displayed in this single image?
Man, I hated those in Highlights Magazine. I still hate that shit.
-
Wait, I only count two now.
Where's the third one?
- [spoiler]The post displayed is not from the topic I'm apparently viewing[/spoiler]
- [spoiler]Apparently I'm at post number 0[/spoiler]
-
The one I saw was Dots 2.0.
-
- Dots 2.0
-
3. missing
-
