How come the back button doesn't work anymore?
-
Ok am I crazy here? If you were looking at a quote in a post, and hit the little up arrow on the right, it'd scroll up to the original post that was quoted. Then you'd hit the Back button and end up back where you were.
Now the Back button goes to the last thread you viewed. This has been DRIVING ME NUTS in the past few days.
How many decades do you think Atwood will need to make a forum that isn't a broken piece of shit? Trick question! He's utterly incapable of it!
-
Platform/browser/etc?
I complained that the back button (or swipe motion, actually) doesn't work on Metro IE (I have a Surface 2) and I got laughed at and told "Who cares? Nobody uses that anyway."
-
I haven't changed browsers since it worked and I got in the habit of doing it like 6 times a day.
-
Also relevant: Spam history setting. If you have "Spam my history every time I scroll the Belgium page" disabled, the only history your browser has is the previous document, not a location in the current one. It doesn't update the history when you click the up arrow; I guess it considers this a form of scrolling, sort of.
Workaround is to expand the replies to the original post, then click the down arrow to go to the relevant reply. Yes, it's a workaround; the way Discourse treats the history is completely broken.
-
Discourse
treats the historyis completely broken.
-
Touché
-
Also relevant: Spam history setting. If you have "Spam my history every time I scroll the ■■■■■■■ page" disabled, the only history your browser has is the previous document, not a location in the current one.
Maybe the setting turned itself off? I didn't go out of my way to do it, but it seems to be off now.
EDIT: no it's still turned off. (Meaning, the checkbox is cleared.)
-
My favorite recent example is this thread:
http://what.thedailywtf.com/t/i-what/7434
All I did was reply in /t/1000 with no quoting, no Markdown, no other shenanigans, and somehow Discourse turned that into its own thread with a couple quotes grabbed from who the hell knows where. Seems about as likely as my headlight switch causing the tires to go flat in the car behind me, but then again, this is Discourse. I gave Discourse a lot of grace about being broken until this nonsense happened.
-
Perhaps it's a sign Discourse is becoming sentient? What with the quote about Jeff having a lobotomy and all....
-
Maybe the setting turned itself off? I didn't go out of my way to do it, but it seems to be off now
The setting looking turned off (ie the checkbox is unchecked) means it's turned on as well as it's turned off.
No, really. I have the setting enabled, and the checkbox is empty.
-
doesn't work on Metro IE (I have a Surface 2) and I got laughed at
Remember, Discourse is the forum software for the next 10 years. Nobody will be using touch-screen tablets 10 years from now, so why should they support them now? (Insert sarcasm tags where appropriate.)
-
Ok?
But the real point is, it don't work no more. It's off, and the URL's not updating until Discourse downloads a new "block" of 20 posts.
BROKEN. SHIT.
-
-
We know, we completely agree. We have been agreeing with you since May.
-
the URL's not updating until Discourse downloads a new "block" of 20 posts
My URL doesn't update then...
-
Yeah I was wrong, it happens when you pause about 5 seconds without scrolling. Which is much longer than I spend looking at the posts if I hit the up-arrow to scroll to them.
-
-
Perhaps it's a sign Discourse is becoming sentient? What with the quote about Jeff having a lobotomy and all....
I wonder, will it be a malicious entity, angry at all the abuse we've sent at it? Or a pitiful thing?
-
I wonder, will it be a malicious entity, angry at all the abuse we've sent at it? Or a pitiful thing?
&Discourse;
doesn't look too malicious to me.
-
Yeah I was wrong, it happens when you pause about 5 seconds without scrolling.
Ditto here. So it's DC crapping itself, since I truly doubt blakey uses Opera on Linux.
Wonderful.
-
Metro IE (I have a Surface 2) and I got laughed at and told "Who cares? Nobody uses that anyway."
Typical. Metro IE is IE, but I guess @ is too dumb to know that.
-
If you have "Spam my history every time I scroll the ■■■■■■■ page" disabled, the only history your browser has is the previous document, not a location in the current one.
Ah, that's what causes that. I've discovered you have to be careful how you close the notifications dropdown--it turns out I was clicking on the blue top of page, and that takes you to the top of thread, and destroys the history. "Oh, you were trying to catch up on 500 unread posts? Too fucking bad. Good luck figuring out where you were."
the way Discourse treats the history is completely broken.
QFT
-
"Oh, you were trying to catch up on 500 unread posts? Too fucking bad. Good luck figuring out where you were."
Yeah, I hate that. My solution is usually lots of paging up until I don't see the blue dots any more.
-
I've discovered you have to be careful how you close the notifications dropdown
I usually leave it open until it closes by clicking on some other link or by refreshing the page. The way I use it, which I'm sure is Doing It Wrong™ by anyone else's definition:
- I usually open the dropdown only when I'm on the topic list. E.g., I just got a notification, but I won't look at it until I'm done typing this and am ready to go off to another topic.
- If the notification is for a Nice Post, I ignore it.
- If it is for a reply, quote, whatever, I find the relevant topic in the list to see if there may be other posts I haven't yet read, because going directly to the reply will lose my place in the topic. If there are more unread posts than replies to me, I click the topic link and read to the end of the topic. (This may or may not result in Discourse thinking I've read the notification; more on that later.) If all the unread posts are replies to me, I click on the notification.
- After having caught up on the topic, I open the notification dropdown again and click on the notification, if necessary, to make Discourse think I've read it.
Yes, this is a somewhat stupid workflow, but it's the best way I've found to both avoid losing my place in a topic and making sure the notifications are dismissed.
-
Yes, this is a somewhat stupid workflow, but it's the best way I've found to both avoid losing my place in a topic and making sure the notifications are dismissed.
+ᶗ
Pretty much describes my workflow, too. The only thing I'd add would be getting rid of PMs created by and in response to flags, which is a problem that you don't have (until someone defers your flag, of course).
-
Yes, this is a somewhat stupid workflow, but it's the best way I've found to both avoid losing my place in a topic and making sure the notifications are dismissed.
QFT
-
My solution is usually lots of paging up until I don't see the blue dots any more.
That doesn't work inside a topic.
-
-
What blue dots do you see inside a topic, that you would be able to use to tell which post you were reading before Disconavigation struck?
-
Probably the unread dots beside the timestamp that fade out when you look at them but sometimes don't.
-
What blue dots do you see inside a topic, that you would be able to use to tell which post you were reading before Disconavigation struck?
They appear between the timestamp and the "+ Reply as linked Topic" link. And they fade away as discourse marks stuff as read. Sometimes server cooties don't allow this.
-
I literally don't think I've ever seen those. Except just right now.
-
Now you'll always see them. It will drive you mad. Especially during server cootie storms.
-
Now you'll always see them.
That was a pretty low thing to do. You'll have to post earworms, probably, to unlower your reputation.
-
server cootie storms.
I've had Chrome installed on Linux a few hours, and within the first like 2 hours it decided the image on the start page for here should be the Infinispinner. It learns quickly. Took Chrome on Windows days to figure that one.
-
doesn't work on Metro IE (I have a Surface 2) and I got laughed at and told "Who cares? Nobody uses that anyway."
Well, they have a point. ;)