CSS WG Blog – Minutes Seattle F2F Wednesday 2017-01-11 Part I: Transforms, Whitespace in a custom property in a variable reference, Geometry interfaces

This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.

Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.

Minutes Seattle F2F Wednesday 2017-01-11 Part I: Transforms, Whitespace in a custom property in a variable reference, Geometry interfaces

By Dael Jackson February 25, 2017 (Permalink)
Categories: resolutions

Transforms

The references to 4×4 matrices will stay in L1.
There was agreement that transforms should apply to flex and grid.
The spec will clarify that transform-origin’s resolved value is used.
Resolved: add transform-origin-x/y/z to transforms levels 1 and (for z) 2, to address issue 29
Chrome just committed a patch which resolves the issue titled ‘transform-origin: 0% not equivalent to 0px is confusing’
Resolved: Add identity transform function to transforms level 2, interpolates with anything, to address this issue
shane to add use counter to Chrome to collect frequency data on compatibility of change for issue 37
The group had three proposed resolution to the transforms interpolation issue (issue 38)
1. Run the transitions
2. Define canonicalization and use the general available transform list and determine if to trigger a transition
3. Similar to 2 but moves it to transitions
- There was originally a leaning to get author feedback to decide between a and c, but it was discovered that browsers are interoperable on a.
- Author feedback will still be sought in case there’s overwhelming consensus that c would be the expected behavior.
Resolved: Resolve issue 38 on option A (run the transitions) from above.
Resolved: matrix() and matrix3d() should be the same primitive in <a href="https://drafts.csswg.org/css-transforms-1/#transform-primitives"this list
Resolved: Perspective will interpolate to perspective, rather than to matrix, interpolated by the reciprocals of the lengths.
Resolved: Follow the spec and match FF which means perspective with a value of 0 is invalid.
Resolved: UAs must introduce near 0 clamping for perspective.

Full Minutes || Spec Referenced

Whitespace in a custom property in a variable reference

TabAtkins will create an example in the custom props specification so that everyone is parsing out the whitespace in a custom property as defined by the syntax specification.

Full Minutes || Spec Referenced