[Webkit-unassigned] [Bug 61561] add support for "on demand" webfonts

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri May 27 12:14:40 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=61561





--- Comment #2 from Brian Stell <bstell at google.com>  2011-05-27 12:14:40 PST ---
Webkit has many layers so I would appreciate some recommendations and guidance on where in the code the pieces would best go.

I need to know if this font is a "load on demand" font. Would it be okay to do this by the extension? Should I create a different type font object; eg, a new subclass? Can I get a recommendation where this should go in the code?

I will need to download the font 'base' (font with removable parts removed) if nothing is already downloaded. I see what looks like font loading code in CSSFontSelector::addFontFaceRule(). Can I just assume this code is enough? Or do I need to do something like change the font object type?

As the page is loaded I need to know this is a "load on demand" font (perhaps by object type). The font object will need to have info on which characters are supported in this font and which characters have already been downloaded. Obviously this info will also need to be in the font file.

The font object will need to be able to record the accessed characters. Where would the best go? Perhaps some of the layout code such as RenderBlock::LineBreaker::nextLineBreak()?

When the base font has been received I need to not request a reflow. Recommendations on where this logic should go? Perhaps CSSFontSelector::dispatchInvalidationCallbacks() ?

When the page has finished loading I need to request the needed data. Where would this go? Perhaps MainResourceLoader::didFinishLoading()?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list