Bug 213772 – The preferred logical width of a text with line-break:anywhere doesn't take kerning into account

• Component: Text
• Status: RESOLVED CONFIGURATION CHANGED

[Fujii Hironori]

The preferred logical width of a text with line-break:anywhere doesn't take kerning into account

[Fujii Hironori]

Created attachment 403171 [details]
test case

The first text has text-rendering:optimizeSpeed, and is rendered without kerning.
The second text has text-rendering:optimizeLegibility and line-break:anywhere, is rendered without kerning.
However, the second text computed its width without kerning and has the extra space.

[Fujii Hironori]

Created attachment 403172 [details]
[screenshot] AppleWin port

[Fujii Hironori]

Created attachment 403262 [details]
[Screenshot] Safari TP 109

[Fujii Hironori]

(In reply to zalan from bug #217136 comment #3)
> In LFC the preferred width computation and the actual layout share the same
> codepath with different constrains, so I'd say yes.

[Ahmad Saleem]

Chrome Canary 119 and Firefox Nightly 120 match each other in above test case while Safari Technology Preview 180 does not.

AppleWin port is gone though it still seems to be an issue.

@Alan - can we move it to 'Radar' to track it?

[zalan]

This is fixed. No extra space at the end of the second line. (IFC progression)

[Ahmad Saleem]

Created attachment 468110 [details]
Safari vs Others

I get this in Safari vs other browsers.

[zalan]

(In reply to Ahmad Saleem from comment #7)
> Created attachment 468110 [details]
> Safari vs Others
> 
> I get this in Safari vs other browsers.
Please file a bugzilla if you believe WebKit's optimizeLegibility implementation produces incorrect result here. By looking at the screenshot, it seems like we push for some advanced ligature, but I am no expert.