WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED CONFIGURATION CHANGED
108074
[Meta] Accelerate complex font path and consider removing simple path
https://bugs.webkit.org/show_bug.cgi?id=108074
Summary
[Meta] Accelerate complex font path and consider removing simple path
Dominik Röttsches (drott)
Reported
2013-01-28 04:52:49 PST
As discussed in
https://bugs.webkit.org/show_bug.cgi?id=37984#c28
and below Nicolas and Behdad suggest to go the Firefox way, optimize the complex font path using caching for shaping results of TextRun and phase out the simple font path altogether. Their argument is, the simple path + the heuristics to change to complex path are too fragile. In too many cases the simple path assumption fails. I am creating a meta bug to discuss and track this.
Attachments
Add attachment
proposed patch, testcase, etc.
Nicolas Mailhot
Comment 1
2013-01-28 08:39:14 PST
BTW anyway wanting to keep the simple path should study African scripts, as they are doing mightily weird stuff on a latin base.
Dominik Röttsches (drott)
Comment 2
2013-02-04 07:23:18 PST
CC'ing Dan. I created this bug mainly to start the discussion - and follow up on the suggestions Behdad and Nicolas brought up in the previous thread. Dan, you created for example
bug 100050
- which probably touches on similar issues - I am not sure this one and similar issues can be solved with workarounds applied to the simple path.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug