I noticed this for the first time just a few days ago.
The keyboard # command pops up a little dialog box, in which you can enter a desired post number, and it jumps directly to that post. This has stopped working. Now, no matter what post number you enter, it takes you to the first post in the thread.
More precisely: It takes you to the desire post, but only for a brief moment. Then the page appears to re-load itself, but leaves you at the top of the thread.
I am using Straight Dope Light theme. Computer is an old-ish MacBook Pro, browser is an old-ish Firefox. This is the environment I’ve been using for a long long time. Nothing has changed on my end that I can think of.
I know that # used to work because I’ve used it. But it doesn’t work for me now.
Now wait a minute. (As I type this, I see you’re in the midst of typing a reply too.) I just noticed this:
If I type # then enter a post number then click on the OK button, it works as expected. But if I enter a post number then press the Enter key, it fails as described above. But that is exactly how I’ve used the # command previously, which used to work. So something has changed.
It just seems like a odd quirky thing to suddenly have problems with. Why would a Discourse update mess with some detail like that? I haven’t noticed a similar problem with other dialog boxes (although to be sure, one doesn’t deal with dialog boxes much in Discourse), and I haven’t seen other problems all of a sudden.
Yikes. That was almost 2 months ago I was seeing this. IIRC, I played with a little bit back then and, IIRC, I was getting inconsistent results that I never quite figured out. I’ll try this again sometime in the Near Foreseeable Future (perhaps later this evening) and I’ll let you know what I find. Quite probably, GreenWyvern is right, that it probably depends on whatever version of something-or-other I’m running here.
Okay, I played around with this some more. I can’t get consistent results, but this is what I am seeing:
When I type # and a post number, sometimes it takes me back to post #1, and sometimes (more often, I think) it just takes me back to the same post I was looking at before.
This is only inconsistently repeatable. If I repeat the attempt, I usually get the same result, but not always.
It seems to happen more-or-less repeatably in some threads, but not at all in other threads. I tried looking at several threads in several categories. In some of these threads, I could not get the problem to happen at all. In others, it happens.
In some cases, it took me to the next-unread post, but I think I was probably already looking at that post. Now, I think it doesn’t matter what posts I have or haven’t already read.
ETA: This thread itself is one in which I am trying this, and seeing some of these anomalies.
ETA2: It looks like the most common result is that it just puts me back on the post I was previously looking at.
ETA3: Note the description in the OP: It actually takes me to the desired post, but only momentarily. Then the screen refreshes, but positioning to the wrong post.
The back button work-around is at least worth mentioning so we know of a work-around. I think the tab-tab workaround looks easier, though, and perhaps more reliable. One never knows exactly what the back button is going to do.
Thanks, @samsaffron ! It’s really weird how something like that would behave differently with different browsers.
Web programming: Write once, debug everywhere!
Did you happen to note the other recent thread in which I mentioned that dragging-and-dropping text from somewhere into a Discourse text box also doesn’t work? See here, including a scenario where it would be helpful: