Minutes Seattle F2F Thursday 2017-01-12 Part I: Transforms
Transforms
- shane will investigate fixing the quaternation algorithm to address issue 33 and the interpolation algorithm to address issue 40.
- Resolved: For animation/rendering purposes, canonicalize
perspective(0)
to perspective(inf)
.
- Resolved: Add
transform-origin-x/y/z
to the level 2 spec (Issue 29).
- Resolved: Close issue 31 no change, as the relevant feature has been removed already.
- Resolved: Issue 32 is closed due to Sydney resolution, change has already been made to V&U.
- Resolved: Issue 34: A zero-degree
rotate()
is treated like an identity transform, relative to other rotation functions. (Similar to how perspective(0)
is now being treated.)
- Resolved: Issue 38: just accept that transitions will run whenever the functions differ, even if the endpoints are functionally identical.
- Resolved: Reject issue 41.
- Resolved: Issue 42: respond that while this does look better, for web compat reasons we can’t change, and we’ll continue to push things that make it easier to avoid matrix interpolation.
- Discussion on naming identity function will happen over github.
- Resolved: Close issue 43 as invalid, now that all transforms decompose with a 4×4 matrix.
- Resolved: Issue 45 is a Geometry issue, with a warning that this function doesn’t work with flattening anyway and should be dropped.
- Resolved: The scale described in issue 44 doesn’t belong in the transform specification as it isn’t used by CSS transforms – instead the fairly simple functions that describe how to extract a scale from a matrix should be described directly in SVG.
- Resolved: Issue 46: change the spec to instead use a UA stylesheet rule to give SVG elements a default transform-box value of view-box (rather than trying to map border-box to view-box).
- Issue 48 had several resolutions:
- Resolved: Static transforms that overflow parent bounds do cause a scrollbar.
- Resolved: An animation that is in fill (finished, or not yet started) is treated same as static, for purposes of transform/bounds/scrollbars computation.
- Resolved: Animated transforms that go out of bounds MAY show a scrollbar during the animation.
- There was a proposed resolution of “Overflow bounds are computed at end of layout, can be increased but not decreased by the effects of paint-level things like transforms.” but the group decided to discuss over the lunch break.
Full Minutes || Spec Referenced
« Previous article
Next article »