This is because this causes the complex text rendering path to be hit (via Font::typesettingFeatures and then Font::codePath). In the EFL backend these complex functions are not implemented. Since EFL uses Cairo with Freetype we can use the simple text renderer to render this text.
Created attachment 102649 [details] Proposed patch
Just pointing out that this bug number is 0x10000!
Comment on attachment 102649 [details] Proposed patch View in context: https://bugs.webkit.org/attachment.cgi?id=102649&action=review > Source/WebCore/ChangeLog:3 > + Use simple text rendering functionality for complex text rendering on Please write title of this bug to here. And, move bug description to below. > Source/WebCore/ChangeLog:7 > + Missing reviewer field.
Informal r-. This will render text with complex texts incorrectly; Arab text, for instance, won't render properly. Compare with other browsers, like Firefox or Chrome: http://ar.wikipedia.org/wiki/%D9%84%D8%BA%D8%A9_%D8%B9%D8%A8%D8%B1%D9%8A%D8%A9
(In reply to comment #2) > Just pointing out that this bug number is 0x10000! It was a lot of fun. :) I suppose this bug must be resolved.
Complex rendering should at least be better these days now that we use HarfBuzz. Dominik, do you know anything about this? We are currently skipping fast/css/text-rendering.html because of this; looking only at the test, we seem to match the results for all platforms except Mac (which is the only one with a "ligature" in the last two lines).
Closing this bug because the EFL port has been removed from trunk. If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.