Support for font-variation-settings has been on by default since Firefox 62, which was released almost two years ago. Are you using a Firefox older than that?
Ah, sorry, I was looking at the wrong item on "Can I Use...", @font-face: font-variation-settings, rather than the "Variable Fonts" item which covers font-variation-settings outside of @font-face rules.
There's a great series of posts going into more detail about Pernosco's design and advantages that is linked to in the final paragraph: https://pernos.co/about/
I am wondering why this isn't getting more attention.
> It appears that the Ryzen PMU just isn't quite accurate enough :-(. rr
> might work OK for some kinds of usage but I wouldn't recommend it.
>
> I'll land the patches I have with a warning for Ryzen users that things
> won't be reliable.
Can someone with a technical understanding describe what's going on here?
Is this a flat-out bug- or does the x86 architecture spec allow for this?
There are minor benefits without ABP. For each page/iframe that is created, we can avoid running the CSS cascade (and share those data structures) for the UA style sheets. It's saves something like 100 KiB per document.
If other add-ons insert a common style sheet into all documents (it's plausible Stylish does something like this? though I've never checked) then we'll again be able to avoid running the cascade and having duplicate data structures for the cascade across different documents.
I just wanted to take the time to thank you for fixing that bug. Since I keep dozens of tabs open all the time, the memory consumption of FF has caused me a lot of pain (the browser gets really slow if it crosses 2.5GB real RAM consumption).
Interesting that Firefox takes the decomposed Hangul and renders it as whole syllables, while Chrome shows them as the sequence of individual jamos. http://mcc.id.au/temp/hangul.png