twistedtree
Guru
I reported this some time back but that thread has been closed. The “New Posts” button behaves differently when clicked from a laptop browser vs a mobile browser, and the mobile operation is really pretty annoying.
In a PC browser (safari or Firefox on macOS in my case) the New Posts button brings up “unread” posts. This is very useful for picking up where you last left off. If you click the little icon next to the thread topic in the summary list, it takes you to the first unread post in that thread. Very useful.
However on a mobile browser (safari on iOS in my case) the New Posts button brings up “most recent” threads, I.e. threads that have most recently been updated, even if I have already read them. And then I click on the little icon next to the title, it takes me to the last post in the thread, not the first unread post. So I need to scroll back and try to figure out what is new and what I’ve read before. Not at all useful, and actually makes using the site difficult.
I know the web site detects mobile browsers and behaves differently, but this is clearly a bug. It’s probably a different SQL query being used in the mobile version to bring up most recent posts rather than unread posts.
In a PC browser (safari or Firefox on macOS in my case) the New Posts button brings up “unread” posts. This is very useful for picking up where you last left off. If you click the little icon next to the thread topic in the summary list, it takes you to the first unread post in that thread. Very useful.
However on a mobile browser (safari on iOS in my case) the New Posts button brings up “most recent” threads, I.e. threads that have most recently been updated, even if I have already read them. And then I click on the little icon next to the title, it takes me to the last post in the thread, not the first unread post. So I need to scroll back and try to figure out what is new and what I’ve read before. Not at all useful, and actually makes using the site difficult.
I know the web site detects mobile browsers and behaves differently, but this is clearly a bug. It’s probably a different SQL query being used in the mobile version to bring up most recent posts rather than unread posts.