Topic List link frozen to search result post number after visiting full search page
-
See post #4 for reproduction steps.
States I had 14 unread posts, but would redirect me to post #18182, 1/3rd of the way through the topic.
Hard refresh did fix it.
-
Hard refresh did fix it
NOTABUG
Also, testing...
No, not the blue bar. Huh. Probably general cooties or something.
Also, do edits/likes count as activity?
-
One more test... Nope. Well, beats me.
-
Just found a way to reproduce the bug, and it involves the full search page:
- Open the search bar
- Type "succinctly" in (without quotes)
- Click "show more"
- Look at the URL for the Likes topic (should point to post #15903)
- Click the TDWTF logo to return to the "latest" list.
- Look at the URL for the Likes topic (should still point to post #15903)
You can also test with the Status thread, it points to post #1317.
-
I had a thread where I navigated to the top before exiting. Later, when there were new posts, it took me to the top again instead of the new posts.
-
Did you go to the full search page at all before that point (and without a new tab or a hard refresh)? It looks like once it has the URL set from a search, it never changes it, no matter how many times you view the topic or when new posts come in.
If it can happen without going to the search page, that's going to be fun to find.
-
...actually, yes, yes I did. Huh. I searched, found the op, went to the bottom, started composing a reply, darted back up to the OP again to check the thread rules, then posted.
-
Okay, seriously, I don't know if it's this bug or what, but it's getting to where I can barely keep track of what's going on. I'm always some bullshit way up a thread when I enter it instead of where I meant to be.
One consistent offender: https://what.thedailywtf.com/t/the-drivers-license-thread/49863/2
I'm always on post 2 of that thread no matter how many times I read it.
-
try posting in that thread? that unstuck it for me last time i was stuck.
-
Try deleting the /2 at the end of that link...
-
Doesn't help when navigating from the topic list…
-
That's the link that got rendered from the index when I tried to go to the latest post, /2 and all. Once I'm there I can just click the bluelevator to get to the bottom, but why is it wrong in the first place?
-
If the topic list actually directs you to post 2, are the further posts in that thread getting read?
-
I read them, yeah.
Since I've posted again, it seems to be working
-
Since I've posted again, it seems to be working
+1 to @accalia for the workaround (discoround? No, that has a negative connotation. Workaround FTW!)
-
Full-page search confuses the record of the latest post you read
This is affecting me heavily on WTDWTF; when I click on a topic that has updates on the topic list, I frequently am taken to a post that is dozens, hundreds, or in one case a thousand posts higher than the actual new post I was trying to reach. This seems to be triggered by visiting the full-page...
-
So, no surprise, that topic is now closed.
After @sam asked you if you could reproduce it on meta.d and linked to a commit to fix something relating to the full page search, someone else chimes in that it fixes a different bug reported in a similarly named topic, and that was all the confirmation needed for Atwood, so he closed the topic.
The commit in question, given the title of the commit and the other bug topic, looks to be aimed at fixing the different bug, not this one.
By the way, this bug still appears to exist on meta.d.
Searching for "workaround reload" will show that topic in the full page search and link you to post #2, then, without a hard refresh, finding the topic again keeps the link at post #2 (when, for a not-logged-in-user, it always wants to put you at the top).
-
By the way, this bug still appears to exist on meta.d.
if that is the case, just flag the topic, we reopen.
-
just flag the topic
not-logged-in-user
I don't have, nor will I have, an account on meta.d.
But since you are now aware that it does not appear to be fixed, you shouldn't need the flag to reopen it.
Just seems a bit overzealous to close the bug before the original reporter gets a chance to respond, especially given that even your post conveyed that you weren't sure it was fixed.
-
There is not one single part of software development Atwood is competent at. I don't know why you'd think he knew triage.
-
Just seems a bit overzealous to close the bug before the original reporter gets a chance to respond, especially given that even your post conveyed that you weren't sure it was fixed.
No, the real problem here is the issue you noted in your
<abbr>tag: a "developer" who had previously been uninvolved in the ticket is the one who closed it. Said individual has been aggressive about closing tickets opened by members of WTDWTF, generally with no explanation. I even know of one case where he deleted a bug report that he admitted was a legitimate bug.
-
grumble grumble
yeah it still happens
posted a reproduction case over on meta
-
You might be confusing it by saying "read marker" in your repro on meta.d.
The link to a topic in the topic list (after performing a full page search, without switching to a new tab or a hard refresh) links you to the post it found for that topic from the full page search, which may or may not be the last post you've read for the topic.
-
whatever. They can ask for more details if they want them.
-
Between my post above where I gave a search (against that bug topic, no less) and the repro steps both here and there, they should have enough to go on.
-
I tried this like 10 times in a row and can not repro, was able to repro prior to my change.
Full page search
Click logo
All urls seem fine
-
I gave better repro steps. You have to have the thread you're clicking on in the search results, that's key.
-
I can confirm that it is still a bug over on meta.d. As @Yamikorune indicates, it only affects topics that:
- You have a last read position in.
- Show up in full page search results at some point.
-
I can confirm that it is still a bug over on meta.d. As @Yamikuronue indicates, it only affects topics that:
- You have a last read position in.
- Show up in full page search results at some point.
The difference between the dev in this thread and the dev that closed that thread is that this dev said "I can't reproduce the bug" and that dev said "This topic is now closed."
-
Indeed. I just figured added confirmation and detail never hurts.
-
The difference between me and the dev in that thread is that I believe you and that dev repaints his bikeshed more often than he eats meals.
