CSS WG Blog – Minutes Tucson F2F: Syntax and Administrivia

Minutes Tucson F2F: Syntax and Administrivia

By fantasai February 20, 2013 (Permalink)
Categories: resolutions

Resolved: User-defined things continue to be matched case-sensitively. CSS-defined things continue to be matched ASCII-case-insensitively, even when defined to exist through UA stylesheet rules or equivalent (e.g. @counter-style rule); such identifiers are effectively ASCII-lower-cased on parse.
Resolved: Font-family names are matched Unicode CI against the font, using C+F casefolding rules with no normalization or locale-specific mappings.
We expect CSS-defined syntax to remain ASCII-only. (User-defined idents of course can span most of Unicode.)

Resolved: Closing brackets in the wrong places are just invalid tokens in the context they’re in; they don’t get special handling. [Update CSS3 Syntax to match 2.1.]
Discussed non-use of grammar productions in CSS3 Syntax, specifically potential concerns for:
- Inadvertent incompatibility with various parser architectures.
- Understandability of spec to authors or others who want a high-level view of the syntactic structure.
- Hooking syntax defined by other modules into the CSS general syntax.
Reviewed current list of differences from CSS2.1 syntax.
Resolved: Add tokens for all the multi-character attribute selector operators to css3-syntax. [Match CSS2.1 / Selectors Level 3]

Full minutes: Part I, Part II

Resolved: Develop text for CSS2.1 PER as open editor’s draft (while continuing to maintain errata). Publish PER when we’re done & have updated implementation report.

Resolved: Meet at TPAC, possibly TPAC-adjacent.
Resolved: Summer meeting in Europe week of 9th September. Tentatively scheduled for Mozilla in Paris, other options on the table.
Resolved: June 5-7 at Mozilla Japan in Tokyo

Full minutes: Part I, Part II

Last updated 2013-02-20 07:06:05