[Webkit-unassigned] [Bug 23755] New: [S60] font's face attibute is converted into font-face declaration incorrectly
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Feb 5 02:33:43 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=23755
Summary: [S60] font's face attibute is converted into font-face
declaration incorrectly
Product: WebKit
Version: 412
Platform: S60 Hardware
OS/Version: S60 3rd edition
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: New Bugs
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: lauri.taipale at digia.com
Reproducible with WebKit versions 413 and 525 on the S60 platform.
If HTML "font" element's "face" attribute contains a font name that has
"independent" numbers in it, e.g. "Font 123 Sans", the font name is converted
into CSS "font-family" declaration incorrectly which causes the font name
parsing to fail and WebKit to fall back to the default rendering font.
When the "face" attribute's value is converted into "font-family" declaration,
font names that have spaces in the name are not properly enclosed in quotes
(').
E.g.
<font face="Font 123 Sans">
becomes
font-family: Series 60 Sans;
when it should be (according to the CSS specs)
font-family: 'Series 60 Sans';
This causes the "CSSParser::ParseFontFamily" method to stop parsing the font
name when it encounters the number part of the font name (in this case "123"),
causing the font name to be truncated, i.e. "Font 123 Sans" becomes "Font".
This then causes the CTextRenderer(Factory) to fall back to the default
rendering font (debugged with WebKit 413).
(If the font name in the "face" attribute is enclosed in quotes (against the
HTML specification), e.g. <font face="'Font 123 Sans'">, then the conversion
and parsing is done "correctly".)
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list