- Resolved: Publish an updated CR draft of css-variables (Issue #6783: Publishing css-variables)
- heycam will create a list of all remaining env variables that need to be added to the environment variables spec so they can be resolved on and the FPWD can be published. (Issue #6729: Publish css environment variables fpwd)
- Resolved: Accept fantasai’s proposal, get it written into spec, have tests updated to match (Issue #6609: Directionality inheritance into Shadow DOM)
- Resolved: Change nesting draft to use open/close brackets, and add a note to show that syntax vs. what Tab would prefer (Issue #4748: Syntax suggestion)
- Resolved: Our preference is for a single syntax for nesting (Issue #4748)
- Resolved: Don’t have nesting om using its own interface; instead, just allow style rule to contain a list of style rule (Issue #4748)
- Resolved: SVG clip-path bounding box units refer to CSS border-box of element to which applied (Issue #5786: “object bounding box” needs to be better defined for CSS boxes)
- The Masking spec editors were given an action to audit the spec for other ambiguities similar to the object bounding box one.
- Resolved: clip-path and masking should follow same rules as backgrounds with regards to box-decoration-break (Issue #6383: Not clear how clip-path applies to fragmented elements)
- Resolved: Take all the “don’t implement this” notes out of Media Queries 5 (Issue #4834: Note/Issue on not shipping early proposals)
- A note will be added to the video-* media queries to state that what is in the spec is likely wrong, but the group hasn’t figured out the right approach yet (Issue #4834).
- Resolved: Skip 0 increments when determining the starting value of a reverse counter (Issue #6738: Automatic start value of reversed list is affected by ‘counter-increment: counter 0’ nodes)
- Resolved: Elements with ancestors of content-visibility:hidden will have no boxes while in top layer. If removed from top layer they get their box back (Issue #6728: Top layer interactions with content-visibility: hidden)
- Resolved: If the subtree of an element contains a top-layer element it is relevant to the user (Issue #6727: Consider top layer elements ‘relevant to the user’ for content-visibility: auto)
- There is agreement that issue #4598 (Static ranges and css-contain) is a problem that should be solved and the solution should be as limited in scope as possible. The result would need to be observable to the author so they can respond and the current proposal doesn’t have that observability. The discussion will continue on github to develop a solution.
- Resolved: Accept iank’s proposal to guarantee full layout algorithm is always forward moving (Issue #6426: Ancestor Layout Loops with Single-Axis Containment)
- Once the edits for issue #6426 are in the spec, a request will be made for FPWD of Contain 3.
- Resolved: Publish WD for Transforms L2
- Resolved: Add dbaron as co-editor of Transforms L1
- Resolved: Add the cssom rules as .name and .namelist (Issue #6576: Cascade Layers need CSSOM support)
- Resolved: It [revert-layer] would revert the style attribute and nothing else (Issue #6743: revert-layer keyword in style attribute)
- Resolved: revert-layer reverts animation origin and nothing else (Issue #6749: revert-layer keyword in keyframes)
- Resolved: Republish Highlight API
- Resolved: Punt attr() and toggle() to Values Level 5 (Issue #6753: Punt attr() and toggle() to Level 5)
↧
Minutes Virtual TPAC 2021-11-03
↧