Websites Discussion
Mark as read, navigate somewhere else, then hit back button in browser
Talk about our websites Serato.com and Whitelabel.net
To talk about a Serato product such as Scratch Live or ITCH please find the appropriate forum area.
To talk about a Serato product such as Scratch Live or ITCH please find the appropriate forum area.
Mark as read, navigate somewhere else, then hit back button in browser
Konix
4:38 AM - 16 June, 2009
Maybe it's just Firefox, or I don't have a setting set correct, or it's a Mac thing, or a combination, but when I click the "Mark Discussions as Read" button to turn all the yellow threads to white, I usually then navigate somewhere else, say another thread, PM box, whatever, but then hit the back button in the browser to go back a page (which is a subforum main page), all the threads are yellow again (after being previously cleared to white).
I'm pretty sure it's something with Firefox, cause it doesn't do this in Safari 4.0, threads stay white after clicking the browser's back button, but it look like Safari actually reloads the page.
I don't know if this is a problem per se, just thought you should know. Slightly annoying to me, but nothing major. I'd use Safari 4.0, but still no bookmarks sidebar and can't live without that so have to stick with Firefox.
I'm pretty sure it's something with Firefox, cause it doesn't do this in Safari 4.0, threads stay white after clicking the browser's back button, but it look like Safari actually reloads the page.
I don't know if this is a problem per se, just thought you should know. Slightly annoying to me, but nothing major. I'd use Safari 4.0, but still no bookmarks sidebar and can't live without that so have to stick with Firefox.
Matt G
6:21 AM - 16 June, 2009
That would be expected if Firefox is caching the page. Normal behaviour (ie you're getting a cached page, with out of date information).
That Safari isn't caching the page is actually more the bug, to my eyes. Although Safari is giving you the correct, up to date information, I think we've got our servers set to allow browsers to cache the pages locally. Although that may have changed.
That Safari isn't caching the page is actually more the bug, to my eyes. Although Safari is giving you the correct, up to date information, I think we've got our servers set to allow browsers to cache the pages locally. Although that may have changed.
nik39
8:48 PM - 17 June, 2009
Actually I like the caching a lot cause it prevents the browswer from trying to reload the page. This can suck horribly if you are jumping forth and back a lot.
Quote:
Slightly annoying to me, but nothing major.Actually I like the caching a lot cause it prevents the browswer from trying to reload the page. This can suck horribly if you are jumping forth and back a lot.