- Resolved: We will spec that grid, flex, and table fragmentation align globally before fragments are created (Issue #6812: Flexbox alignment and fragmentation)
- Resolved: We will not truncate margins at any break when aligning globally for fragmentation (Issue #6812)
- alisonmaher will reach out to print formatters to get feedback on the above resolutions. If they have a different opinion the group will revisit.
- Resolved: The mix interpolation function will only be used for top-level values with various discussed caveats. mix() is the name of the top level interpolation (Issue #6700: Validity of generic interpolation function mix())
- The general agreement from the github conversation for issue #6513 (getComputedStyle and fragmentation) was to select a simple value to return, create exceptions where compat demanded, and direct authors toward existing fragment-aware APIs if they need an accurate answer. On the call, there were concerns about breaking compat since these properties have existed for a while, even though there isn’t interoperability. Suggestions were to do a deeper dive into properties and specify a compat-friendly requirement or to specifically state browsers handle this differently and there is no interop. Discussion will continue on github to reach a decision.
- Resolved: When an inline box is split by a block box, offsetWidth and offsetHeight will include dimensions of block box (Issue #6588: Needs more details for offsetWidth and offsetHeight)
- Resolved: Property and fontface rules always work in an @container rule (Issue #6827: What happens to other @rules inside @container?)
↧
Minutes Telecon 2022-01-05
↧