Bug causing threads not to show as read

[cpratt]

Finally saw the breadcrumb but it's almost at the bottom of the page. It works that way or by swiping one more time and hitting the back button. I know what to do now. Thanks.

There should be one at the top where I showed it in the photo, and one at the bottom down below similar threads. If you don't see the one at the top, I'd like to know what type of phone it is and which browser it uses. It may be that the specific browser is not taken into account in the mobile version of the site. On my iPhone on Safari and on Firefox does show the upper breadcrumb.

 

[M-MAN]

Found the upper breadcrumb too. It's all the way to the top like you said. I think it's easier to just give it a swipe after reading the last post as that will get me to the bottom and clear it when I hit the back button. The computer will be different but I think the breadcrumbs will be handy there.

 

[cpratt]

Found the upper breadcrumb too. It's all the way to the top like you said. I think it's easier to just give it a swipe after reading the last post as that will get me to the bottom and clear it when I hit the back button. The computer will be different but I think the breadcrumbs will be handy there.

I'm not sure if that will work. The back button normally has to be avoided on the net now unless the page you are going back to doesn't require an update. You said it worked to go to the bottom and hit the back button, but I can't reproduce that. They still show as unread for me if I do it that way since the previous page has not been updated from the server. I use the back button constantly, but that is because it doesn't matter if the last page is updated in what I'm doing (like reading a manual from an index page for the sections of the manual).

In the old system, it was spotty whether it would "update". That was because they were traditional links that show visited versus unvisited (shown in underlined blue or amber/red). The browser would sometimes show that a page has been read by keeping track of the page link locally on your device and then changing the color. This wasn't reliable though and lots of times people would complain about that, it's not that well supported in browsers now. There and here, the reliable way to so browse "forward", meaning using a link. The breadcrumb concept was introduced (and actually required by certain powerful companies that control the net) to get around this problem. A really good example with browsing forward versus using a back arrow to show a previous page from cache, is a shopping cart. If you browse backward after purchasing, something bad can happen since the previous page has no awareness that you completed the purchase, so as a result, you can buy the same thing twice accidentally, then it can be worse than that, like being charged twice but maybe not even get two invoices. The same principle applies to the read or unread status on the previous page. It has no awareness that the page has been read. Browser cached pages are very valuable in not having to load more stuff over the net which speeds things up greatly on a slow circuit like I have, but with it comes this price of non-updated pages.

I haven't tested what we've talked about on a phone because the screen is too small for me to read and my phone won't work in my office (no cell signal), but I will play around with it at some point.

 

[stevieb49829]

I'm 95% there using a new "brainstorm" that has brewed up after learning exactly how this happens. I'm testing now on a different system just for that. When it works I will unceremoniously install it which I think will clear up a massive amount of confusion over what is read and what is not, even for moved threads.

I'm horrified that this happened because it's caused so much confusion in an already traumatic transition for people.

Chris, you may not hear it often, but THANK YOU. ALL OF YOU!! We/I really appreciate the time and effort you folks have spent to get this new/improved monster into a useable state. Here's hoping no one goes off screaming into the night, shredding their hair. Again, my personal thank you! steve

 

[cpratt]

Chris, you may not hear it often, but THANK YOU. ALL OF YOU!! We/I really appreciate the time and effort you folks have spent to get this new/improved monster into a useable state. Here's hoping no one goes off screaming into the night, shredding their hair. Again, my personal thank you! steve

Very much appreciate the sentiment.