Fragment of a discussion from User talk:Nx
Jump to: navigation, search

Aargh. Refreshing the page in ancient firefox on antique fedora causes the most recent thread to disappear. That's another one of the reasons I've been avoiding talk pages with LQT.

Carry on, you're far better equipped to deal with this than most of us, I suspect.

Sprocket J Cogswell (talk)01:03, 14 October 2012

That's not just your computer; pre-update, I had that problem too.

Star of David.png Radioactive afikomen Please ignore all my awful pre-2014 comments.01:04, 14 October 2012

Oh, THAT bug. It's actually not caused by your browser, it's caused by LQT being stupid. You see, when you add a comment, a thread gets bumped, which means its last modified timestamp is updated. But when you click on a link in recent changes, that link has a timestamp in it, and it only displays threads before that timestamp. But the thread you were trying to get to now has a newer timestamp, so it disappears. In your case, the url you refreshed probably contained a timestamp (the offset= part), and when you refreshed, the thread disappeared because I bumped it.

-- Nx / talk01:07, 14 October 2012