Minutes TPAC 2012 Part I: Administrative, Prioritization, and HTMLWG
- Assigned actions for next steps in switching over all specs.
- Co-chairs surveyed WG members about their priorities; results are posted by glazou with VSI = Very Strong Interest, SI = Strong Interest, LI = Low Interest, NI = No Interest.
- Top items are Flexbox, Transforms, Transitions, Animations, and Conditional Rules, regardless of formula.
- Layout modules (Flexbox, Multicol, Regions, Grid) always in top ten
- Middle shifts around depending on weighting formula, but Level 4 specs consistently towards the bottom of the list
Identified several places where coordination is needed:
- Selectors. This is largely handled due to last year’s Selectors 4 FPWD, and subsequent edits that aligned the HTML spec with that.
- Scoped style sheets. Various aspects of this are either underdefined or incorrectly specced. Several CSSWG members recommended to drop it from the HTML5.0 timeline. Aside from the HTML syntax for invoking scoped styles, many things need to be defined that belong on the CSS side, specifically:
- Handling of scoped selectors (mostly handled in latest Selectors 4)
- Potentially, CSS syntax for changing how selectors are scoped.
- Scoping the cascade (will be drafted into CSS3 Cascade soon, but no draft yet exists as of TPAC 2012)
- Handling of various globally-scoped at-rules such as
The third issue was about communication. Historically, the HTMLWG has put things in their spec that affect the interpretation of CSS (or, in some cases, extend CSS) without notifying the CSSWG of such changes or additions, giving the CSSWG no opportunity to review and send feedback or to incorporate such changes into its own specs. The HTMLWG countered that the CSSWG should file bugs about things that are wrong (once they find out about them) and escalate things using the HTMLWG process.
Present in this discussion were the CSSWG, two of the HTMLWG co-chairs, one of the HTML5 editors, and W3C’s Philippe Le Hégaret.
« Previous article
Next article »