Motion Path
- Resolved: Add “at position” to path(), shape(), and ray() (FXTF Issue #504: offset-position + circle())
- Resolved: Add ‘normal’ keyword to ‘offset-position’ (FXTF Issue #504)
- Resolved: Default box used by ‘auto’ value of ‘offset-anchor’ is box specified by ‘transform-box’, so it matches box used by ‘transform-origin’ (FXTF Issue #503: anchor-position – which box?)
- Resolved: offset-position: auto uses offset-anchor point (FXTF Issue #501: offset-position:auto has bad behavior)
- Resolved: offset-anchor: auto uses transform-origin point (FXTF Issue #502: offset-anchor:auto is nonsensical)
- Resolved: Use half width/height for horizontal/vertical rays, interpolate for other angles (FXTF Issue #363: The description of contain flag in ray() function)
- Resolved: For sides value, have snugness (FXTF Issue #363)
CSS Display
- Resolved: Land the PR, after addressing pending feedback (PR #8257: Define ‘reading-order: auto’)
- The concern about needing reading-order:auto on the children will be raised in a separate issue.
Align, Flexbox, & Grid
- Resolved: first/last baseline takes from the first/last item (rather than taking highest/lowest baseline) (PR #8341: Improve container baseline finding algo)
- Issue #7641 (How to determine the last baseline of a flex container with different alignment groups) should be resolved by the above PR. There are some cases that need further investigation and will have separate issues opened.
Shadow Parts
- In discussing issue #7922 (Make `::slotted()` a combinator), it was raised that there is existing confusion with named slots as illustrated in this codepen. The group discussed this for the remaining time on the call, but did not come to a resolution. A separate issue will be created to track this topic.