CSS WG Blog Minutes Sydney F2F 2016-02-01 Part I: Web …

Minutes Sydney F2F 2016-02-01 Part I: Web Compat Challenges, Tables, Colors, Transforms

Web Compat Challanges

• tantek presented several types of web compat challenges the working group faces.
• The first type is problems like 0 vs 0deg in CSS gradients, where there is a common dependency on the web that breaks spec compat. These are handled on a case-by-case basis, and considerations include:
  • Some cases can be seen as an opportunity to make behavior more author-friendly, if it’s clear that this is author-expected behavior. (0 vs. 0deg seems to be such a case)
  • The amount of pages that are affected should be taken into account in decision making – though there was a difference of opinion as to how much breakage is acceptable.
  • The reason for the original decision should be reviewed before any changes are made.
  • Implementers seem willing to make more severely-breaking changes if the benefit to the platform is significant.
  • In regards to gradients, this was narrowed down to three options on which there was a straw poll:
    1. Don’t change gradients. Keep angle-parsing quirk to transforms
    2. Allow 0 || angle for gradients as well as transform functions, but not in properties in general
    3. Allow 0 to parse as angle everywhere (including not in functional notations)
  • Resolved: Angles can drop unit when value is 0
• The next type of challenge is when there are changes made for web compat purposes, but they’re not reported to the working group.
  • Though business decisions needs to be made, there was a request for an e-mail to the working group informing them of a deviation, even if no effort is made to follow up, because this way at least the problem is being tracked.
  • It was also suggested that the working group be more receptive to this kind of e-mail.
• The third challenge was how do we get member sites to stop depending on CSS vendor prefixes. The example for this issue was the bug browsers had to introduce to keep Gmail working.
• The discussion started by trying to figure out how to put more pressure on member organizations for problems like this, however with many member organizations being very large, their CSSWG representatives often don’t have power to make the changes.
• The conversation changed to how to give more agency to those in the working group to encourage change in their organizations.
• A step to move forward in some -webkit- cases is to update at least the behavior to match the spec; this reduces the implementation burden for vendor-prefixed properties.

Full Minutes

Tables

• Resolved: Add gregwhitworth and franremy as editors of CSS Tables and copy into CSSWG ED repo
• There was a desire to have headers and footers repeated; the only disagreement was if it should be a ‘should’ or a ‘must’ level.
• Resolved: contain applies to table cells

Full Minutes || Spec Referenced

Colors

• RGB color section outside of 0-1 is being addressed in a spec written by Chris and therefore doesn’t need to be explained in the CSS3 Colors.
• There was a desire to create a new way to specify colors and color profile and work will start to come up with language on a proposed approach. Once written the proposal will go into Colors 4.
  • SteveZ will also get feedback from Adobe on how they expect wide gamut colors to be handled.

Full Minutes || Spec Referenced

Transforms

• smfr gave a status update for the spec stating he’s still looking for implementor feedback on preserve-3d and some assistance from someone who knows matrix math.
• Resolved: Republish Transforms

Full Minutes || Spec Referenced

« Previous article Next article »