Conversation

At any rate, while I think Firefox's approach is kind of cute, my boss has kind of convinced me that a better solution is to force a ligature break when there's is a change to the inline style. So both Chrome and Firefox are probably doing it wrong. 😅
2
1
Although in linking that doc, Safari is probably using Core Text – which *might* use an alternate standard for shaping Myanmar. Can't remember the specifics though. Regardless, the relevant bit is that scripts like this do glyph substitutions, and Safari is breaking those.
2
1
Replying to
hard to know what's also actually a bug or a feature in these cases, for me anyhow - chrome's behaviour re: my original example is broken in that intent failed (f[iretr]uck is funny, fi[retr]uck is annoying), firefox's is cute, safari seems optimal. but beyond english? no idea :D
1
1
Show replies