Post by Breadknife on Jun 23, 2014 4:08:42 GMT
A side-note to the original issue, although almost certainly unrelated... I tend to get get erroneous "bubble numbers" a lot (and even "New" labels on the Participated line) which I put down to my browser (Firefox, before you ask) or connection through the ISP (awful, as I've often mentioned, so maybe sometimes gets adversely proxied slightly) displaying a slightly out-of-date version of some information.
edit: So... yeah, as well as everything else, seemingly fixed, "shift-refresh" seems to be pretty universal (on all browsers I use regularly enough to notice) as a "please don't short-cut this process, actually do go get the latest version of this page, don't just assume you have the latest version in cache due to a dodgy application of Cache-Control or HEAD method calling" thing...
(The "futzing with the settings thing" is something I'm agreeing is probably the answer to the OP, though. Note at least two other points of reported weirdness seen over the weekend.)
{Example}e.g. when viewing a page on a thread and (much prior to my recent message about editing) editing a post, then returning to the thread, I don't get to see the edited version of the post unless I shift-refresh the page (to force re-download). And when I'm expecting a "New" Participated, I find it useful to go to the Messages front-end, and when I'm expecting a new message I find it useful to go to a (ideally participated) thread, but sometimes it seems I get (or don't get) the notification that I actually got a previous time I was on the page concerned (it looks like there's a new message, when there's no new Participated item, but going to the Messages screen I find that this presents the more recent state of all messages now read but with a New Participated notification, which on visiting any such thread (correctly) shows no new post of that kind, but the aforementioned new message bubble).
Confused yet?
Confused yet?
edit: So... yeah, as well as everything else, seemingly fixed, "shift-refresh" seems to be pretty universal (on all browsers I use regularly enough to notice) as a "please don't short-cut this process, actually do go get the latest version of this page, don't just assume you have the latest version in cache due to a dodgy application of Cache-Control or HEAD method calling" thing...
(The "futzing with the settings thing" is something I'm agreeing is probably the answer to the OP, though. Note at least two other points of reported weirdness seen over the weekend.)
