- #1
- 3,369
- 2,567
Behavior of the browser's "Back" button.
I've noticed some new behavior of PF as of the last two or three weeks or so.
When I look at a list of threads on PF (whether it be a list of threads in a subforum, or my own "subscribed threads"), recently updated threads that I have not read yet have their thread name displayed in boldface. After catching up on one of these threads, and clicking on the browser's "back" button, PF's behavior used to be such that the thread name in question was no longer displayed in boldface.
But now when clicking the browser's "back" button the thread name in question is still displayed in boldface. It's not until I refresh the page (or re-click on "subscribed Threads") that the displayed thread name goes to normal (un-bolded), indicating that I'm all caught up on that thread.
Given my current habits, this causes me to inadvertently re-read threads that I just finished reading moments before.
I'm guessing that maybe this behavior was intentional: Don't indicate a change relative to the user's cache when clicking the browser's "back" button in a possible attempt to reduce server load.
But I don't know if that is correct. Is this behavior intentional?
I've noticed some new behavior of PF as of the last two or three weeks or so.
When I look at a list of threads on PF (whether it be a list of threads in a subforum, or my own "subscribed threads"), recently updated threads that I have not read yet have their thread name displayed in boldface. After catching up on one of these threads, and clicking on the browser's "back" button, PF's behavior used to be such that the thread name in question was no longer displayed in boldface.
But now when clicking the browser's "back" button the thread name in question is still displayed in boldface. It's not until I refresh the page (or re-click on "subscribed Threads") that the displayed thread name goes to normal (un-bolded), indicating that I'm all caught up on that thread.
Given my current habits, this causes me to inadvertently re-read threads that I just finished reading moments before.
I'm guessing that maybe this behavior was intentional: Don't indicate a change relative to the user's cache when clicking the browser's "back" button in a possible attempt to reduce server load.
But I don't know if that is correct. Is this behavior intentional?