Closed
Bug 384679
Opened 18 years ago
Closed 10 years ago
Trailing whitespace ignored in font names
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: sharparrow1, Assigned: jtd)
References
()
Details
<!DOCTYPE html>
<style>
.a {font-family: Arial\a\9\20}
</style>
<div class="a">b</div>
This font gets recognized as Arial; however, I don't think I have a font on my system that has a name with a tab or a newline in it.
Not sure if this is a style system bug; it might be a GFX issue.
From http://www.w3.org/TR/CSS21/fonts.html#font-family-prop :
# If quoting is omitted, any whitespace characters before and after the
# font name are ignored and any sequence of whitespace characters inside
# the font name is converted to a single space.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
|
||
Comment 2•12 years ago
|
||
I believe that the report is valid. Whitespace tokens are indeed ignored, but quoted whitespace should not be removed from the parsed value of identifiers. The spec was since updated to clarify:
# If a sequence of identifiers is given as a font family name, the computed value is the name converted to a string by joining all the identifiers in the sequence by single spaces.
Flags: needinfo?(dbaron)
Yes.
Did bug 280443 fix this?
|
Assignee | |
Comment 5•10 years ago
|
||
(In reply to David Baron [:dbaron] (UTC-7) (needinfo? for questions) from comment #4)
> Did bug 280443 fix this?
Yes, it did. :)
|
|
Assignee | |
Comment 6•10 years ago
|
||
Fixed by changes in bug 280443, reftest landed on bug 384682 includes the case noted here (i.e. trailing escaped space).
Status: REOPENED → RESOLVED
Closed: 18 years ago → 10 years ago
Resolution: --- → FIXED
|
||
Updated•10 years ago
|
Assignee: nobody → jdaggett
Target Milestone: --- → mozilla32
You need to log in
before you can comment on or make changes to this bug.
Description
•