Minutes Telecon 2023-03-15
View Transitions
- Resolved: If an element if fragmented into more than one element, it does not participate in View Transitions (plus note that we want to do such things in the future) (Issue #8339: Capturing fragmented elements)
- Resolved: If an element is involved in a transition, the `view-transition-name` constraints are enforced during the transition (Issue #8548: Define the constraints which must be satisfied by a named element during the transition)
- Resolved: Conditions are checked per-frame; transition is skipped if other constraints are broken (Issue #8548)
- Resolved: The view transition fills the viewport and captures clicks (Issue #8278: UA CSS should size ::view-transition to 0x0)
- Resolved: Target pointer events to the document element (Issue #7797: User input should be ignored when rendering is suppressed)
- Resolved: User agent can limit rasterization for performance limitations, but must size the element as if it was fully rasterized (Issue #8561: Define behavior when capturing image for a large element)
- Resolved: Rasterization must cover at least the visible area of the viewport (Issue #8561)
- Further discussion is required to determine how to handle painting overflow in issue #8561. There needs to be a bit more understanding of both author expectations and fingerprinting implications.
Full Meeting Minutes
« Previous article
Next article »