Closed
Bug 465463
Opened 16 years ago
Closed 16 years ago
[@font-face] style matching with local font should always use @font-face rule style
Categories
(Core :: Graphics, defect, P4)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jtd, Assigned: jtd)
References
Details
(Keywords: fixed1.9.1)
Attachments
(2 files)
534 bytes,
text/html
|
Details | |
12.18 KB,
patch
|
vlad
:
review+
vlad
:
approval1.9.1+
|
Details | Diff | Splinter Review |
Fonts defined with @font-face rules should always use the style settings defined by the @font-face rule, not the style implied by information in the font.
Example:
@font-face {
font-family: test;
src: local(HelveticaNeue-Light);
font-weight: bold;
}
In this case, this font should be used as a weight 700 font, not as a weight 200 font.
Assignee | ||
Comment 1•16 years ago
|
||
Should see Helvetica Neue used when bold is selected. Comic Sans shows instead because the underlying weights are being used instead of the @font-face defined weights.
Assignee | ||
Updated•16 years ago
|
Priority: -- → P4
Assignee | ||
Comment 2•16 years ago
|
||
Rather than use existing font entries, create a new one when src local() is used in @font-face rules. The new font entry uses the style attributes defined by the @font-face rule rather than the underlying font data. Also, support both Postscript and full font names. Full font names will work across platforms but Postscript font names are supported by WebKit, need both to match Safari. New reftests included, assumes tinderbox machines have Bitstream Vera Sans but won't fail if they don't.
Attachment #359707 -
Flags: review?(vladimir)
Attachment #359707 -
Flags: approval1.9.1?
Attachment #359707 -
Flags: review?(vladimir) → review+
Assignee | ||
Comment 3•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•16 years ago
|
||
Argh, remember to add reftests...
http://hg.mozilla.org/mozilla-central/rev/f050934dd42e
Attachment #359707 -
Flags: approval1.9.1? → approval1.9.1+
Assignee | ||
Comment 5•16 years ago
|
||
pushed to 1.9.1
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/71c7facd1403
Keywords: fixed1.9.1
You need to log in
before you can comment on or make changes to this bug.
Description
•