| Summary: | [Chromium-mac] applying any -webkit-font-feature-setting changes font rendering/layout | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Levi Weintraub <leviw> | ||||
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED WONTFIX | ||||||
| Severity: | Normal | CC: | bashi, eric, glenn, leviw, schenney | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
does it's presence trigger slow (complex) text path which when not present uses fast path? if so, that could explain much (In reply to comment #1) > does it's presence trigger slow (complex) text path which when not present uses fast path? if so, that could explain much I'm fairly certain this is the case, but the selection bug indicates that the fact that it triggers this change isn't properly understood by all of the rendering code (RenderText::canUseSimpleFontCodePath returns true, for example). |
Created attachment 195346 [details] Test case Just having a valid -webkit-font-feature-setting in affect changes font layout and introduces selection rect bugs. This only appears to affect Chromium Mac.