If I read a post and then go back to the forum the thread/post is not being marked as read and I have to manually 'marked all posts as read'. Any reason why this is not working?
No one is "blaming the browser". The site knows what threads have you have read (when signed in), the browser does not simply because it can (and does) use cache -- that is what it is for. This is standard-operation-procedure and very much expected when you click the back arrow in most standard browsers.
stuartw said:Surely the site should know that i have read a post and therefore show as read. To blame the browser is not really the answer.
I agree with Phil it looks the site works as expected. The approach "it's my workflow and I require it has to work as I want" doesn't work here simply because it's in conflict how web technologies, tools and standards evolved (not always in a correct and system way) many years ago.
What you require is to request the site to regenerate the page again, so you will see the updated page (with an article display as read). But Back button only tells to a browser "display me a previous url". There is no standard that it has to be refreshed page, so browsers displays page from cache as written by Phil. In fact, there is no error in terms of implementation, it works as expected.
It's not rare problem. If you will go into web dev forums, you will find plenty of similar discussions how to implement some feature and at the same time be compliant with old fixed tools (like Back and Forward buttons) and maintain complexity balanced with a performance. There are different ways how to solve this issue available, but it's never win-win, but always quid pro quo. Some web forces people to use own "in page" back button and to ignore the browsers' one, another tries to hack Back button (bad idea because it's not standardized, just ugly hack often not functional) or some pages are marked as "non cacheable", so the browse has to request a site every time for such page. Maybe it sounds fine but the result is seriously higher traffic and consequently lower performance, so it's also treated as not recommended in the most situations.
Personally I click on a forum name on top a page (... > Communities Feedback Forum in this case), which leads to a refreshed page.
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
I was obviously expecting too much!!
Unknown said: Personally I click on a forum name on top a page (... > Communities Feedback Forum in this case), which leads to a refreshed page.
And that is what I have been using recently to get over the problem. Doesn't always work though!