Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMake font family property value iteration more robust #193
Labels
Comments
|
I believe that #1109 fixes this. |
SimonSapin
added a commit
to SimonSapin/servo
that referenced
this issue
Jan 3, 2014
* Using .connect(", ") just to use .split(",") later is silly.
Keep it a vector.
* The 'font-style' property can not be both italic and oblique.
Use an enum instead of two booleans.
SimonSapin
added a commit
to SimonSapin/servo
that referenced
this issue
Jan 3, 2014
* Using .connect(", ") just to use .split(",") later is silly.
Keep it a vector.
* The 'font-style' property can not be both italic and oblique.
Use an enum instead of two booleans.
therealglazou
added a commit
to therealglazou/servo
that referenced
this issue
Feb 20, 2014
* Using .connect(", ") just to use .split(",") later is silly.
Keep it a vector.
* The 'font-style' property can not be both italic and oblique.
Use an enum instead of two booleans.
ChrisParis
pushed a commit
to ChrisParis/servo
that referenced
this issue
Sep 7, 2014
Remove a trailing '/>'
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The specification allows for single and double quoting of font names, and in some cases these imply different semantics for font matching. Currently, quotes are ignored and only comma-delimited font family names will be matched.
The parsing details are in CSS 3 Fonts, Section 3.1.