Site doesn't load correctly on Chrome after Win11 24H2 update

[lordodogg]

For some reason, this site sometimes does not load correctly on the first try on Google Chrome after updating to Windows 11 24H2, which was finally released to my computer last night.
It loads in either an incorrect format, or in what appears to be a version of the site with all the CSS stuff (or whatever it's called) removed (meaning just the images and text display on a white background in Times New Roman font).
Pressing the reload button causes the site to load correctly.
This is affecting some other sites I visit, so it's probably more of a Chrome issue or Windows issue.
This did not happen on Windows 11 23H2.
My Chrome browser is up to date.

 

[lordodogg]

Here is a screenshot I just managed to get of the site not looking as it should after I just clicked on the Post Thread button:

 

[HIFI]

clear cache, cookies? sign back in?

 

[lordodogg]

will try that

 

[lordodogg]

so far it's working fine now

 

[Almighty1]

It's a Windows 24H2 issue and not even a Chrome issue itself as 24H2 has lots of issues as Beta Insiders is still on 23H2.

 

[lordodogg]

I see. That could explain why it took so long for the update to become available to me via Windows Update in the first place.
IIRC, it came out back in October but was quickly pulled due to reports of BSOD's and was delayed by a few weeks or so, after that delay they then began to do the "release in waves".

 

[harshness]

It's a Windows 24H2 issue and not even a Chrome issue itself as 24H2 has lots of issues as Beta Insiders is still on 23H2.

This is more likely a XenForo issue in which it is generating cookies for 23H2 that aren't compatible with its code customized for 24H2.

I imagine that XenForo looks at the user agent metadata (specifically the OS version) and behaves differently when the OS version changes. This is neither a Chrome nor a Windows issue but a problem with how XenForo interprets (or gags on) its own cookies. It is also possible that they've narrowed the user agent data checks so tightly that there isn't a code branch for 24H2 yet and it must use some fallback code.

As most of us have experienced, wonky cookies are one of XenForo's biggest PITAs.

 

[Pepper]

I've seen plenty of websites act like that on occasion over the years, long before 24H2 was available, it's most likely a Chromium rendering engine got confused thing since it usually works correctly upon refreshing the page.

 

[harshness]

I've seen plenty of websites act like that on occasion over the years, long before 24H2 was available, it's most likely a Chromium rendering engine got confused thing since it usually works correctly upon refreshing the page.

If I'm not misreading, the cookies had to be whacked before the problem went away.

 

[Almighty1]

This is more likely a XenForo issue in which it is generating cookies for 23H2 that aren't compatible with its code customized for 24H2.

I imagine that XenForo looks at the user agent metadata (specifically the OS version) and behaves differently when the OS version changes. This is neither a Chrome nor a Windows issue but a problem with how XenForo interprets (or gags on) its own cookies. It is also possible that they've narrowed the user agent data checks so tightly that there isn't a code branch for 24H2 yet and it must use some fallback code.

As most of us have experienced, wonky cookies are one of XenForo's biggest PITAs.

Good points. Forgot all about the User Agent Metadata part.