I find that it breaks if the browser feels a need to redownload the page (e.g. if you shift-reload the page, or there's an explicit expiry in the HTTP headers that came with the HTML body) as the back-end has noted that, upon serving you the page with the 'first unread' post upon it, you have now (conceptually) now 'read' this message, and all messages up until the latest available (or page-end, should that be sooner). The next full request for "next unread in this thread" is thus served with an adjusted content (including #unread point).K-R wrote:I'm pretty sure on some forums the anchor is actually just #unread, not a specific post, which is why I thought it might break. But obviously that wouldn't apply here, since it does anchor to a particular post.
But if the browser is happy to stick with the cached source (plus the by-now-locally-cached page-realligning images and other embeddeds of various kinds), it may well render again (and near instantaneously) with identical contents as you ended up with the first time, and then shift the scrolling viewport appropriately. As described.
But, as ever, depends on all those niggling little dependencies and subtly differing behaviours as to how good or bad it is at obeying various expectations...
(I still want a forum that has user-shiftable thread bookmarks. Details follow in Spoiler, due to length...
While I'm here, several times since I discovered by a comment on tjis thread that egosearch has been (again?) fixed I've composed a little thing about (as far as I can tell) it apparently being A-Ok for me now. Yet I didn't want to write a mere contextless "thanks" message for the fix, and clutter the place up. Nor jinx the fix by doing so. Well, I might still have jinxed it (and I note others seeing inconsistencies, still) but a little fluff down here at the end of a longer post, where no-one will even read it, avoids the contextlessness issue, methinks. Thanks!