CSS WG Blog – Minutes Paris F2F 2017-08-03 Part II: Fonts, Display, Counter Styles

Minutes Paris F2F 2017-08-03 Part II: Fonts, Display, Counter Styles

By Dael Jackson September 2, 2017 (Permalink)
Categories: resolutions

Resolved: @font-face rules without src descriptor should remain in the om, but should not be used for font matching (Issue #1133). Likewise @counter-style rules.
Resolved: Change font-synthesis to all pairs of keywords and no-keywords. (Issue #1641)
Resolved: Make default values: weight (off), style (off), small-caps (on), make the initial value ‘weight style’, and add keywords no-weight, no-style, and no-small-caps. (Issue #1641)
Resolved: Font variations will be both properties and descriptors. (Issue #1652)
Briefly discussed issue of variation axes that are font-specific and the fallback problem (which for features is solved by @font-feature-values)
Resolved: Rollback to previous state with CSSStyleDeclaration and unmerged interfaces, requiring get/set calls (no .property interface) for @font-face rules in the OM. (Issue #825)
Resolved: font-weight is mapped to actual fonts as follows (Issue #1579)-Split the weights into three categories:
1. light – < 400
2. medium – 400 <= x <= 500
3. bold – > 500
- For light, first search from x => 0, then x => 1000
- For medium, search x=>500, then x => 0, then x => 1000
- For bold, first search from x => 1000, then x => 0
Resolved: Font selection algorithm has different behavior during animation than Fonts 3; we will add a note to that affect in Fonts 4. (Issue #1579)

Resolved: All font-* properties are reset by the font shorthand, except font-presentation and font-synthesis.

Resolved: Leave ‘display’ syntax as-is for #1496
Resolved: For 1246, inlinification of ‘block flow’ goes to inline flow-root aka inline-block, blockfication of inline flow-root & inline-block go to ‘block’
Resolved: For 1486, issue is moot because 1246 resolution was reverted (above)
Resolved: ‘inline flow-root’ serializes in getComputedStyle as ‘inline-block’
Resolved: Accept 1550 “flow never establishes a BFC. Instead, all cases which require a BFC are handled by switching the inner display type to flow-root at used value time via becoming a formatting context.”
Resolved: Move “becoming a formatting context” section back to css-contain, mark ruby/inline as open issues to figure out.

Resovled: Same resolution as yesterday (The language of a counter is computed based on the language of the element that the counter applies to at the point of retrieval.)

Last updated 2017-09-02 11:55:48