- Resolved: We will have 2 separate objects; one for rules without a block and one for rules with a block (Issue #6576: Cascade Layers need CSSOM support)
- Resolved: Reverse the prior resolution. Unlayered styles are highest priority (Issue #6284: Reconsider placement of unlayered styles, for better progressive enhancement?)
- While discussing issue #6284, the group agreed that the author control of priority was necessary in the first level of the spec since there are strong use cases for any order and therefore authors needed to be able to override the default.
- Resolved: Leave the spec unchanged with dot syntax (Issue #5791: What is the appropriate syntax for appending to nested layers?)
- Resolved: Presentation hints into their own origin between user and author in cascade (Issue #6659: Cascade priority of presentation hints vs. tree scopes)
- Resolved: Keep “layers” and close issue no change (Issue #5840: Layers terminology bikeshed)
- Resolved: Use cq as the prefix (Issue #5888: “container width” and “container height” units)
- There should be guidance created to determine when a unit should be created in order to avoid an explosion of units.
- Resolved: Accept proposal in ED. Split range syntax and attributes to new issue (Issue #6396: Define a syntax for style-based container queries)
- Resolved: Add a matchContainer method as proposed in issue. Keep issue open to decide if need new observer or if we can reuse the existing (Issue #6205: Similar to window.matchMedia, Container Queries should have a similar method)
- Resolved: Add the new attribute of highlight type which is an enum (Issue #6498: Figure out how highlights are exposed to the accessibility tree)
- Resolved: Add spelling-error, grammar-error, and highlight (Issue #6498)
- Further discussion about how the highlights are exposed in Issue #6498 should be added to the TPAC meeting agenda with the APA group.
- Resolved: Take scientific notation and match serialization of JS (Issue #6471: Serialization of large numbers should use scientific notation)
- The group didn’t think auto-darkening should be linked to forced colors mode since auto-darkening appears to happen at paint time. Discussion will continue on issue #6664 (Forced colors mode usage beyond high contrast mode).
- Resolved: min-height:auto just has special behavior that allows child %s to still resolve, and it’s not a precedent to apply to all the other content-based keywords. (Thus, we’ll remove, or possibly keep-but-reverse, the note that’s currently in the spec.) (Issue #6457: Definiteness of min-height: min-content)
- Resolved: The offsetWidth and offsetHeight should be computed out of the principal css box (Issue #6588: Needs more details for offsetWidth and offsetHeight)
- Resolved: It should include all fragments (Issue #6588)
- Discussion will continue on Issue #6588 on how to answer how to decide if a block is split does the block doing the splitting get included in the calculation
↧
Minutes Telecon 2021-10-06
↧