[Webkit-unassigned] [Bug 79021] New: Web font is not used in rendering for the first load
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Feb 20 02:42:25 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=79021
Summary: Web font is not used in rendering for the first load
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: CSS
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: yuzo at google.com
The example in https://developers.google.com/webfonts/docs/webfont_loader#Example doesn't work as expected for
- WebKit r108205 + Safari 5.1.2 on OS X 10.6.8
- Chrome 19.0.1041.0 dev on OS X 10.6.8
That is, the text is rendered in the web fonts only if the page is reloaded.
Safari Version 5.1.2 (6534.52.7), Firefox 10.0.2, and Opera 11.61 work as expected.
Reproduction steps:
1. Clear the browse cache (Option+Command+E for Safari).
2. Open the attached webfontloader.html.
3. Observe that the text is rendered in local font.
4. Reload webfontloader.html.
5. Observe that the text is rendered in Web fonts.
I observed the following:
For the fist load, CSSFontSelector::getFontData is called *before* CSSFontSelector::addFontFaceRule.
For the second load, getFontData is called *after* addFontFaceRule.
HTMLLinkElement::setCSSStyleSheet is called from
CachedCSSStyleSheet::checkNotify for the first load, while from
CachedCSSStyleSheet::didAddClient for the second load.
I guess layout should be done after the stylesheet is loaded?
(This is likely related to http://code.google.com/p/chromium/issues/detail?id=114928 )
--
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