See, what gets me is the "is known to cause issues" banner.
One, no it isn't.
Two, that's not a standard feature anywhere. They added that themselves.
So this must be intent. The only "issues" Firefox's strict mode causes is for advertisers whose cookies get blocked. Which should not, and never has in my experience, stop Twitter or other websites from functioning correctly.
Alright, /r/firefox speculates (and console readout supports this) that because they moved Twitter to X.com but were too lazy to move pictures and other assets from twimg.com, Firefox correctly sees they're trying to load from a third party and CORS-blocks them.
Which is Firefox's strict mode working as intended and the issue here is Musk insisting on this absurd name change and being too lazy to go all the way.
Add comment