safari issues

[mustafa0x]

Is safari support planned? I noticed that unfortunately it has many rendering problems.

جزاكم الله خيرا

[aminanan]

This happens when there are a cursive lookup with the RIGHT_TO_LEFT flag set and a cursive lookup with the RIGHT_TO_LEFT flag clear.

As an example suppose we have the following cursive feature.

feature curs {  
  lookup cursivejoinrtl;  # RIGHT_TO_LEFT flag set between Hah, Meem, Yeh and final Meem
  lookup rehwawcursivecpp; # RIGHT_TO_LEFT flag clear between Waw and Hah
} curs;

The word وحميم is rendered as follows with HarfBuzz (I changed the position of Hah to highlight the problem).

With Safari it is rendered as follows.

If the order of the lookups is reversed the result with Safari is as follows (This remains correct with HarfBuzz).

The OpenType specification doesn't describe exactly what to do in such a situation but it seems to be a bug with Safari especially for the first case.

[mustafa0x]

جزاك الله خيرا

I can file this at https://bugs.webkit.org. Is there a reduced test case, or should I file an issue and attach the entire font file?

[khaledhosny]

Is this a Safari-specific issue or (more likely) a CoreText issue and so would affect more macOS apps (like TextEdit or Pages)?

[aminanan]

I tested it with TextEdit in macOS Sonoma 14.3. I had the same problems. It seems to be related to CoreText.

[khaledhosny]

I’d report it Apple using feedback assistant. They usually fix these kinds of issue when reported.

[aminanan]

Thanks @khaledhosny. I reported a bug to Apple using the Feedback Assistant.