Open
Bug 1021539
Opened 10 years ago
Updated 2 years ago
fix parsing of obscure cases of escaped font family names
Categories
(Core :: CSS Parsing and Computation, defect, P5)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: jtd, Unassigned)
References
Details
From bug 280443, comment 75 https://bugzilla.mozilla.org/show_bug.cgi?id=280443#c75 > > > > - // { namelist: "\\,\\;", single: true }, > > > > - // { namelist: "\\{", single: true }, > > > > - // { namelist: "\\{\\;", single: true }, > > > > - // { namelist: "\\}", single: true }, > > > > - // { namelist: "\\}\\;", single: true }, > > > > > > Why do these tests with the escaped symbols not work? Or are they invalid? > > > > I don't think these are valid idents, so I don't think they are valid as > > part of a font family name. Other browsers spit out syntax errors for these > > also. > > I think they are, according to css-syntax. See the "\" case in > http://dev.w3.org/csswg/css-syntax/#consume-a-token. Please file a > followup for this (although I am surprised that doesn't work already). Need to figure out whether cases like the ones below are invalid syntax or not: font-family: \,; font-family: \{; font-family: \};
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•