Discourse quirks
-
At some point we're going to have to stop posting about Discourse and start posting about Funny error messages or something.
-
http://what.thedailywtf.com/t/i-will-just-leave-that-here-discourse-error-message/1670/
Why not both?
Filed under : [with discourse not even the sky is the limit as it is a barrier to reading] (#tag)
-
The amount of free material Discourse gives us between its technical issues, its legion design issues and Jeff's asshattery, we've got enough material to sustain TDWTF through at least the first year of the next 10 years of TDWTF (bearing in mind TDWTF is 10 years old)
-
https://meta.discourse.org/t/logs-page-now-404s-take-2/17542
That topic has got a rather disproportionate number of views for such a recent topic, and given the actual subject of the bug (an admin function). Can't think why...
https://meta.discourse.org/category/bug reverse-ordered by view count:
Rather shamefully, someone - it appears - has seen fit to delete the take-one version of that bug report.
-
The amount of free material Discourse gives us between its technical issues, its legion design issues and Jeff's asshattery, we've got enough material to sustain TDWTF through at least the first year of the next 10 years of TDWTF (bearing in mind TDWTF is 10 years old)
Well, to be completely fair, it was the same with CS. And in another ten years, if we're still around, we'll switch to a then-new buggy heap of shit and it'll all start over again.
At least this one, if you press backspace it only deletes one character.
-
Also, "+ Reply as new Topic" is awkwardly off to the side instead of sitting next to the Reply button, as if they are two completely separate things
Users might click one instead of the other, so it's not a good idea to put them side by side.
-
You say that, but the amount of times I've middle mouse clicked the reply as a new topic opening a new tab is actually embarrassingly high.
-
To be completely fair, that's not the same as CS.
CS is terrible, yes. But most of its issues are implementation only issues. They're not fundamental changes in paradigm with piss-poor design that literally encourage bugs and inconsistencies.
For example, having three completely separate formatting options in the same post is always a recipe for disaster, especially when there's no boiling down to a single master format. It tries to mash badly-sanitised HTML, plus Markdown, plus bbcode without doing any kind of intermediate parsing to a single definitive, sanitised version and this encourages bugs.
-
Also, "+ Reply as new Topic" is awkwardly off to the side instead of sitting next to the Reply button, as if they are two completely separate things, instead of being two variations on the same idea, which they are.
Not if you have browser zoom at < 100%. See if you can spot it:
Reproducible here on Firefox and Chrome.
-
Given the overlapping onto the post divider, I'd almost classify that as a bug.
-
I know CSS can be a bitch at times. And shit sometimes gets pushed where it shouldn't be. But... LOOK HOW MUCH ROOM! LOOK HOW MUCH FUCKING ROOM THERE IS! JUST EXPAND THE FUCKING GUTTER TO THE RIGHT OF THE PAGE, YOU DUMBASS.
Sorry, irate today.
-
LOOK HOW MUCH ROOM! LOOK HOW MUCH FUCKING ROOM THERE IS! JUST EXPAND THE FUCKING GUTTER TO THE RIGHT OF THE PAGE, YOU DUMBASS.
It is irritating how much space gets completely wasted on both sides of the page.
-
It is irritating
how much space gets completely wasted on both sides of the page.FTFY
-
Some things are also wonky when you're zoomed out (as I normally am).
I didn't comment on zooming issues because I'm sure zooming was not a considered use case - i.e. it's doing it wrong.
-
Users might click one instead of the other, so it's not a good idea to put them side by side.
I also just realized that it's off to the side to be next to the links to other topics.
Maybe it wasn't such a bad idea.
Or maybe they could be icons like the rest of the controls? Curved-left arrow for reply, Curved-right with a plus for new topic?
-
I didn't comment on zooming issues because I'm sure zooming was not a considered use case - i.e. it's doing it wrong.
Careful - you might give them ideas about hijacking the browser's implementation of zooming.
*shudder*
-
I'm sure zooming was not a considered use case - i.e. it's doing it wrong.
Considering they disabled zooming on mobile devices, you're not too far off.
-
-
okay, so how did you actually do that?
I just tried this in Chrome, Firefox and Browser in Adriod 4.3 on a tablet (so that means desktop mode) by pinching my fingers (and doing the oposite... whatever you call that) and it didnt change... am I TRWTF?Filed Under: Also, your phone is watching you watching it, that is perverse! | Did you get that watch the phone to do things to actually work? I tried the scrolling once and got nothing but a headache from throwing my eyes and head around...
-
okay, so how did you actually do that?I just tried this in Chrome, Firefox and Browser in Adriod 4.3 on a tablet (so that means desktop mode) by pinching my fingers (and doing the
oposite... whatever you call that) and it didnt change... am I TRWTF?Chrome on Android 4.3, Galaxy S3 (Mobile mode).
Either the two finger pinch or the 1½ tap+slide work.
Did you get that watch the phone to do things to actually work?
Not really.
-
okay, tried it on Chrome, Galaxy Note 3 Neo (Android 4.3, mobile mode) and it didnt work... is that some kind of Admin-only thing? Can you reproduce it after logging off?
Filed Under: This is a Discourse quirk... so not even derailing this topic!
-
Refer to:
@ChaosTheEternal said:<meta name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no">
That is sent down for regular users on both Desktop and Mobile view, which disables zooming on mobile devices. Likely a combo of user-scalable being set to "no" as well as them saying the min and max scale are 100%.I can't say if that comes down for admins, or if the browser on your phone ignores it. But both Chrome for Droid Maxx (Android 4.4) and Safari for iPad (iOS7) listen to it, and zooming is disabled.
If I want to trust a StackOverflow answer, apparently disabling the zoom lets Android skip the delay when it's waiting for a double touch and handles clicks immediately. Not sure for iOS though. And there are other options to allow fast-clicking while still having zoom enabled.
-
Chrome on Android (possibly other browsers too) has "Force enable zoom" as an accessibility setting, which lets you zoom in and break the layout regardless of what the meta tags specify.
-
-
Chrome on Android (possibly other browsers too) has "Force enable zoom" as an accessibility setting
That it does, and it does work. Maybe @PJH has it enabled? It isn't by default, which is why I couldn't zoom on Android.
I'll have to check when I get home to see if my iPad has a similar option for Safari.
-
-
Is highlight-and-drag-and-drop broken on Discourse?
It's not brillant use of the browser, but I used to do it all the time and now it doesn't work in Discourse posts. It still works on most other websites.
Am I doing it wrong or am I Doing it Wrong™?
-
why does Discourse disable zoom in the first place? Zoom is an availability feature and should be prioritized before design, right? I am just asking because some of you are able to instantly quote Jeff on stuff like this...
Filed Under: Quoting Jeff on Discourse is like a SuperPower to CLOSEDWONTFIX topics
-
They broke highlight-and-drag-and-drop if you have the "enable quote reply" option turned on (the button that shows up over whatever you highlight, as long as what you highlight is only in the body of one post).
-
As far as I remember a lot of people complained about it in the first Discourse-posts... So yeah, at least it was broken. Might still be since I never use it. Try finding the posts via Discourse Search function... at least you wont have time to ask another question ever again...
Filed Under: Discourse is always right unless it isnt in which case you are doing it wrong!
-
Because instead of using a more reasonable fix like what I mentioned (putting a min-width on the top bar) to stop it from wrapping so terribly when zoomed in (like you can see in @PJH's screenshots), I guess they decided to go scorched earth and disable zooming.
As for an official posting about it, I couldn't tell you, I'm not going to go lurking around on meta.discourse just to see if I can find it.
-
Afair its not disabled on my desktop pc... as I already opened a bugreport about zooming somewhere... so why disable it on mobiles (that are smaller and therefor offer less textsize to read to begin with? Was it just the technical problems that might come up trying to stop a desktopbrowser to stop zooming? Are Mobile-Users not as good a market as Desktopusers? Does that even make sense? Scratch that... but keep the thought....
Why disable something on mobile devices that works on Desktop-PCs and would actually make sense on mobile? Add a freaking banner that says: "Oh boy, you zoomed in and we screwed up... the layout might not be 100% accurate anymore" and ship the thing >.<
Filed Under: I dont even know why half the things I complain about bother me... but they do somehow
-
Why disable something on mobile devices that works on Desktop-PCs
.. as pointed out previously, zooming doesn't 'work' (as expected) on desktop PCs.
-
Ok, Safari does not have an option, but iOS itself does. Three finger tap to zoom, three finger drag to move where you're zoomed, and three finger double tap then stretch or contract to adjust zoom manually.
It's not very usable to me.
-
So a program giving you incorrect information in any manner, is A-OK with you?
It's only OK for project schedule updates, because no one can handle the truth about those.
-
It's only OK for project schedule updates, because no one can handle the truth about those.
But those aren't programs giving you incorrect information, which means the original question stands.
-
At some point we're going to have to stop posting about Discourse and start posting about Funny error messages or something.
Maybe we can lure the Lotus Notes guy back?
-
But those aren't programs giving you incorrect information, which means the original question stands.
That's what I said.
-
I know. I was sort of agreeing with you. It's still too early, not enough sleep and lots of banging and crashing making it hard to concentrate.
-
If you middle click the "Keyboard Shortcuts" item on the hamburger menu, shit don't work. It opens the current page in a new tab.
How old does a thread have to be to get a Necrophile badge for posting in it?
-
How old does a thread have to be to get a Necrophile badge for posting in it?
No badges, but we've got toasters:
-
Six months?!
That's ... really long. I'd say excessively so.
-
Actually, I guess this is more of a bug than a quirk.
All the other hamburger menu buttons open in new tab when middle-clicked.
Oh well.
-
That's ... really long. I'd say excessively so.
It's the default (hence the white background to the textbox - you make have noticed yellow backgrounds in some of my other screenshots from /admin.)
-
#1 sign of Discourse Syndrome, you start calling "bugs" "quirks".
-
Ok, so how the fuck did that happen?? I typed and submitted it as default font size.
-
Lines starting with # are considered headers and get big.
Also, lines of text before a Markdown line separator (---) also get big.
-
That is just annoying. So why did it not show that in the preview window? Everything looked fine until I clicked "Reply".
-
Because you apparently expected the preview to be an accurate representation of what your post would look like, and we can't have that.
-
@Intercourse said:
That is just annoying. So why did it not show that in the preview window? Everything looked fine until I clicked "Reply".
The client and server bakers are different implementations and occasionally they drift apart.