Bitcoin Forum

ㅤ

This issue had already been posted by Pmalek. (Visit the link below)
Small bug with the highlighting of forum subjects/thread titles (https://bitcointalk.org/index.php?topic=5298598)

The bug was only in Chrome browser and theymos fixed it (https://bitcointalk.org/index.php?topic=5298598.msg55795763#msg55795763).
Maybe, the bug has appeared again.

Edit:
I just opened some unread topics in different boards. In my side, it's working normally.

Given that he said he couldn't find exact documentation, it's possible that there's some extension/browser nuance that happened to bypass the prefetch restriction.

Not necessarily Chrome: I know a few other browsers will try to index pages for faster load time.

I figured it might have been Opera. Check this setting in your browser, and make sure it's turned off:

Preload pages for faster browsing and searching
https://i.imgur.com/4eM85vF.png

did you open that thread in new tab and when you come back after that the 2nd post was looking like it is opened already?
or you just clicked that?

it was happened with me too. some of the posts which I didn't checked looked like they were checked. at one point I was almost believed that I am hacked and someone else using my account and reading posts.
now I think it was all because of using Opera.

CTRL+F12, type "preload", click on "Cookies and other site data".

It's in your settings.

Bear in mind, also, that Opera was based in Chromium.

Sounds like it could be a Chrome-specific issue, since I've never, ever seen a bolded subject line that I can recall, and I don't use Chrome.  In any case, it doesn't sound like a major problem (plus it's one that Theymos is apparently aware of), so it'll get fixed in its own sweet time. 

At least we're not under that spam attack anymore.  That was even more annoying, with all of those threads getting bumped with SEO-type spam.  I'm hoping that doesn't happen again anytime soon.

I had it happen to me back in December in the thread that hosseinimr93 linked to. I just tried to reproduce the bug again and I can't do it. It seems it's fixed. I tried it on Chrome and Firefox just now and the threads below the last one I open remain with dark highlighting (unread).

If it's bothering you too much, use Firefox or Chrome for now. You can try and PM theymos, he was really quick to fix the issue when I experienced it.

I can confirm the same thing is happening with my Opera.
Interesting thing is that if you open one topic and then go back and refresh, the topic below that is also marked as read. I tested it 3 times, here is the result.
https://i.imgur.com/mRMEl9E.png

Test on Version:73.0.3856.284.
---------------------------------
Updating to Version:73.0.3856.329

Still following the same pattern.

It's annoying that browsers are doing this prefetching without any way for sites to signal that they shouldn't, but it's even more annoying that each browser has a separate way of indicating it via headers, and it's all very poorly-documented. In the case of Opera and apparently some versions of Safari, it seems that a prefetching request can be identified if it has a Sec-Fetch-Dest header but does not have a Sec-Fetch-User header. Bitcointalk.org blocks such requests now. (If anyone starts seeing random 403s, this may be the cause; let me know right away in that case.)

As far as I can tell, there is no reliable way to distinguish between prefetch requests and normal requests on these browsers. This is a browser bug; complain to them. There's nothing I can do without totally changing the way topic-visited-tracking works.