Ask help for strange issue about "new" label/tag

[Sebastiii]

Hello,

I'm from forum where it's SMF 2.0.15 in use, I didn't know very well PHP/SQL but I run into a strange issue lately and would like to know what can be the culprit

In some section of thread (by default not visible when user are not register and logged) when new post are present from subscribe thread:
- Opening a thread from the section (not visible to public), make other "new" to be marked as seen.

I have tested on :
- Different browser
- Different user
- Private navigation
- Delete cookie
- Different computer

It's random but always happen, it's like opening thread1 make as read thread2 but it's not always the first thread, it can be the 4th of the list that make read the first one.
A body of mine, tried to analyze the situation from logs, etc. and find nothing wrong.

When it happens from the same site but on different too, the IP wan stay the same, this is really weird and what can be done to try to nail down this kind of issue ?
Once one user logged and not multiple so what can be wrong lol

Thanks for any hint or help on what can be the root cause
Cheers.

EDIT: forgot to add that it happen on normal right user and also with privilege one.

[Illori]

if you "read" the most recent topic and no one else makes another topic for a while, it is possible for that topic to be left marked as unread. is this what you mean? if so this is completely normal.

[Sebastiii]

Thanks Illori and sorry for my english, nope, it's not what I meant

Trying to explain a bit more :
- There is a section with 10 messages unread (marked with label "new")
- When I click to read the firs one (for ex) but it can be another one with label "new"
- Reading the post go back to the list of topic inside this session and it acts like I have read the 2nd one while it's not true.
- Of course, the real one I have read is marked as read

Doing that with other post make other post as read along with the one I have clicked.

In final for 10 post (unread) reading 4 or 5 post make them all marked as read.

But it's random and sometimes it works like it should : mark only the one I have read and not the other.
I don't know what it happens and from what I suppose and see, it seems to happen to only section where user need to be logged/registered to see that section

The word section is maybe not a correct word, I meant it's a specific part of the forum not visible until we are logged/registered.
Thanks

[Kindred]

That is not normal behavior and I can not reproduce the problem

What is your site url?
Mods installed?

[Sebastiii]

Hi Kindred,
The site URL is: http://www.attrape-songes.com/forum/index.php
Need to look how I can see the list of mod installed but the latest was mention (for tagging).

Infos sur la version:
Votre version du forum: SMF 2.0.15
Version courante de SMF: SMF 2.0.17
Version de GD: bundled (2.1.0 compatible)
Serveur de base de données: MariaDB
Version MySQL: 10.2.36-MariaDB
PHP: 5.6.40
Version du serveur: Apache

Thanks.

[Sebastiii]

Finally, I was able to reproduce it here too, let me show you by a video done right now
https://youtu.be/Mdqrr-NEe9I

So, I'm using middle button to open in a new tab or right click on link to open in new tab does the same
Like you can see opening a thread, mark as read the one just below the clicked.

This is on EDGE, need to test on other browser from here, but I was able to reproduce it

[Kindred]

this would seem to be an issue with your browser since I have never seen that behavior and can not reproduce it in Edge, FF or Chrome.

[Sebastiii]

I'm using the latest Edge version and tested also on computer at work (latest Win10 version)
So yes, it can be Chromium based issue after all, I have redo my test and it doesn't only on my rig but chromium engine, testing along with Brave and it's the same.

So do you know what can be the issue for those engines ? I can try to submit a bug report, I have a register to other forum (Xenforo) didn't run into this issue, but I'm not sure what to tell and supply as good information to try to nail down the bug.

I'm trying to look commit change because it happens around 23 or 24 november and I'm not sure how Edge upgrade their source !

Can you try on Chromium based software ?
Thanks in advance

[Kindred]

Seriously, I just tested 4 sites using Edge and Chrome

I think it's something specific to your installation of Edge....

[Sebastiii]

Ok thanks Kindred
Tested on different rig (clean Win10 for a customer) the latest Edge base on Chromium and it happens, no clue but Chrome works so something change recently (I suppose) on Chromium based browser.
Again thank you that you have tested on your side will try to debug on my side, not sure if I will be able to

Hoping that in between a fix will be made on Chromium (if it's the origin of the issue ofc )
But fresh Win10 along with tested on other computer not the same Wan IP (different place using remote connection (Anydesk) ), it's a really crazy weird issue

Will keep you in touch if I find something

[shawnb61]

Mods installed?  Theme used?  Does it do this on the default theme?

I seem to recall while back we found a mod that did this...  It was querying the next message in a way that caused it to be flagged as read... 

[Kindred]

Shawn -- if you want the video he linked, he actually made it happen here on the SimpleMachines.org site....

I definitely can not recreate it in Edge, Chrome or Firefox on this site or on any other,  but since he can do it here, it pretty much has to be something in the browser -- I just can't imagine what.

[shawnb61]

I was just able to reproduce it...  It's a thing...

For me, it *always* flags the next post as read.  No exceptions.  For me, it's not visible, though, until I hit the browser refresh button.   That's when the flags disappear.   (2.0 only, not 2.1)

This is sounding very familiar, but I haven't found the old thread. 

[Kindred]

strange....  I literally can not reproduce it on any browser.

Wonder what the differences in our setting are?

[shawnb61]

I get this on the new Edge browser (Blue swirl, not e - 87.0.664.55 (Official build) (64-bit)) and on Chrome (Version 87.0.4280.88 (Official Build) (64-bit)).

I have not seen it on FF (83.0 (64-bit)) or on Pale Moon (v28.16.0 (2020-11-24)).

Exact same user ID (& thus settings) & forum. 

I do see some variation on the web vs localhost (much more consistently on localhost).  I also see some variation on whether I sit on a page longer or not (if I go back & forth very quickly, it may not happen). 

Possibly a Chromium thing???  I do know they've been experimenting with speeding up forward/back in the latest versions, & this might be related. 

[Sebastiii]

I get this on the new Edge browser (Blue swirl, not e - 87.0.664.55 (Official build) (64-bit)) and on Chrome (Version 87.0.4280.88 (Official Build) (64-bit)).

Thanks for confirming too I was started to be crazy lol

I have not seen it on FF (83.0 (64-bit)) or on Pale Moon (v28.16.0 (2020-11-24))
Possibly a Chromium thing???  I do know they've been experimenting with speeding up forward/back in the latest versions, & this might be related.

That's the idea that comes in my mind too, this is weird but happy that you was able to reproduce on your side
if we can confirm it's a Chromium issue, how we can report them ?
I know that some this on code can trigger hidden one on other code so maybe it trigger an old bug on forum code ? Is this possible too ?

Sorry @Kindred, I forgot to mention to do F5 (refresh) and without this priority information, for sure you can't reproduce it, good @shawnb61 mention it 

[Kindred]

yeah... It's very strange...    I did all the same steps, including the f5 reload. Still can't reproduce it. (and yes, I have the blue swirl edge (Version 87.0.664.55 (Official build) (64-bit))

edit...
just updated to  Version 87.0.664.57 (Official build) (64-bit) and I was able to reproduce ONCE out of 20 tries....

[shawnb61]

It's not browser flakiness, as I initially thought.  There are actually 2 DB updates to log_topics vs 1 as well, logging what has been "read".  Interesting.

[Sebastiii]

It's not browser flakiness, as I initially thought.

Strange then, it should be happening always right ?

There are actually 2 DB updates to log_topics vs 1 as well, logging what has been "read".  Interesting.

This is interesting and thanks to try to find where can be the cause

just updated to  Version 87.0.664.57 (Official build) (64-bit) and I was able to reproduce ONCE out of 20 tries....

Thanks for confirming too even if it happens not like quite always like on my side.
I did have an SSD so maybe files access is faster locally at least, but no real clue

[Sebastiii]

A great member from our forum seems to maybe found the cause of this issue, need to give him more test to do but when he added line from 2.0 template to 2.1, this issue appear too on 2.1 local version forum .

So when he confirms me that it close to 99% related, will report back
Thanks to him