Minutes Overflow Breakout 2025-01-22
- Resolved: Spec scroll-marker-contain (Issue #10916: Creating scroll-marker groups within which to select an active marker)
- Resolved: Adopt everything in the Oct 30 comment (Issue #11098: What is the active :checked marker when some markers point to elements within different scrolling containers?)
- Resolved: Only propagate the scroll into view for a scroll marker up to the common ancestor scroller of the targets (Issue #11138: Limit scrolling to the associated scroll container when activating a marker)
- Resolved: For a 2D scroller, we will define an algorithm that uses a primary direction that defaults to the block axis (Issue #11198: Active marker in 2d scroller?)
- Resolved: ::scroll-marker-group applies containment when it is in-flow only (Issue #11166: Can we relax size containment on ::scroll-marker-group?)
- Resolved: The document.activeElement is the scroll container for a focused ::scroll-marker or ::scroll-button. :focus matches only on the specific focused pseudo-element. :focus-within matches on the ::scroll-marker-group for ::scroll-marker, and the scroll container and all ancestors for both ::scroll-marker and ::scroll-button (Issue #11361: :focus and :focus-within styles with focused scroller pseudo-element)
- There were some concerns expressed that the proposal for issue #10868 (What counts as “immediately preceding” for `block-ellipsis`?) would create inconsistent definitions, however time ran out before the group could discuss further.
Full Meeting Minutes
« Previous article
Next article »