My browser / operating system: Windows NT 10.0, Chrome 114.0.0.0, No Flash version detected

Sometimes, certain scratchr2 pages just stay like they were before the purple update. This fixes itself on reload.

Case in point:

This is probably caching.

CST1229 wrote:

(#2)
This is probably caching.

This page didn't even exist before the update, and the QaS page (where this also happened) worked fine with the purple update before it got blue and after.

mybearworld wrote:

CST1229 wrote:

(#2)
This is probably caching.

This page didn't even exist before the update, and the QaS page (where this also happened) worked fine with the purple update before it got blue and after.

That's not how web browsers work. Regardless of which page you're loading, if they both point to the same CSS file, they both read from the same cache.

If you fully clear your browser cache, do you still see old blue?

test_104 wrote:

(#4)

mybearworld wrote:

CST1229 wrote:

(#2)
This is probably caching.

This page didn't even exist before the update, and the QaS page (where this also happened) worked fine with the purple update before it got blue and after.

That's not how web browsers work. Regardless of which page you're loading, if they both point to the same CSS file, they both read from the same cache.

If you fully clear your browser cache, do you still see old blue?

But why would it cache and apply it only sometimes?
About fully clearing, I don't know, I'll have to try it out

Scratch causes some things on the server side too. That might be what causes this.

Edit: it seems that when the CSS is served from the following URL, it's purple:
https://cdn.scratch.mit.edu/scratchr2/static/__7c0bf135becb6330562ada83eab5a1c1__/css/main.css

And this one is still blue:
https://cdn.scratch.mit.edu/scratchr2/static/__0a3d9844a1f76cfc70114b19220a898f__/css/main.css

I was just about to say what Maximouse just said.

It's a bit weird that theey have multiple URLs to serve CSS from, but I guess that's why.

test_104 wrote:

(#7)
I was just about to say what Maximouse just said.

It's a bit weird that theey have multiple URLs to serve CSS from, but I guess that's why.

I assume that's so that browsers don't cache old versions of existing CSS files, however the server might cache entire pages with those old CSS URLs.