I think the lack of broader Unicode support is a Chrome issue. Works fine in Firefox and Safari. I don't know if there's a way around that, but if anyone has any ideas, I'm all ears.
Noto uses separate fonts for different scripts, so in order to get consistent Noto display I think you need to set up your CSS to specify Unicode ranges to use specific Noto webfonts.
Thomas Phinney Usually Safari and Chrome behave exactly similar in handling CSS and DOM. They even share the same bugs. The difference is, that Chrome caches very aggressively (DNS, redirections, CSS, JS). But this can't be the reason, because my Chrome is open since months with ~200 tabs.
I have MacOS Mojave 10.14.6. On my MacAir High Sierra it's the same.
On my remote iMac with Mojave the Phoenician doesn't display in Chrome, but works in FireFox and Safari. No extra fonts installed. There must be a difference in the handling of webfonts.
Strange, this morning I checked a post and the original posted text looked like a different font than Noto—just the regular body text, but not the title or even the bold in the body.
When I activated the FontFace Ninja extension to check, it then switches to Noto. It only happened to one post, I looked at a few others and they seemed to display the font fine. So, maybe not a big deal. (MacOS 10.14.5 - Safari 12.1.1)
Screenshots below (ignore the different sizes because the image are different dimensions).
Comments
Maybe it’s just time to change browsers. sigh.
This makes it tricky to even notice for the majority (Chrome users) but irritating to us Firefox people.
I am trying to think of what might cause that:
I have MacOS Mojave 10.14.6. On my MacAir High Sierra it's the same.
On my remote iMac with Mojave the Phoenician doesn't display in Chrome, but works in FireFox and Safari. No extra fonts installed. There must be a difference in the handling of webfonts.
Chrome:
FireFox:
I can't even find the file location from where TextEdit, TextWrangler and the command line take Noto Sans Phoenician als fallback.
When I activated the FontFace Ninja extension to check, it then switches to Noto. It only happened to one post, I looked at a few others and they seemed to display the font fine. So, maybe not a big deal. (MacOS 10.14.5 - Safari 12.1.1)
Screenshots below (ignore the different sizes because the image are different dimensions).
BEFORE:
AFTER: