4 ms·
For that visit, Windows 11 with Firefox developer. Ublock Origin and Noscript, with some combination of previously allowed and default-blocked script sources. I
by zbrozek 3y ago
For that visit, Windows 11 with Firefox developer. Ublock Origin and Noscript, with some combination of previously allowed and default-blocked script sources. I didn't really investigate what was missing to mess with the case, but allowing all scripts on the page cleared it.
Just a weird novelty impact that I hadn't seen before, not really a big deal. Also I retract "invert". I went back and looked again and it's definitely not inverted. Check it out!
https://zlnp.net/serve/weird-case.png https://zlnp.net/serve/weird-case.png
- dcre 3y agoOoh, very cool. Looks like you're overriding the font at the browser or OS level? We suspect that has something to do with it. If you look at the raw HTML response, which is what should be getting rendered when you have scripts turned off, you can see that the casing is normal. The mystery to me is why turning scripts back on would fix it. Maybe that overrides your font override and changes it back to our font.
- zbrozek 3y agoI'm not aware of any font overrides (that's not something I typically fuss with) but now you have me suspicious that I don't know my own setup!