CSS WG Blog Minutes Telecon 2023-03-20

Minutes Telecon 2023-03-20

Scroll Animations

• Resolved: Reduce default scoping to ancestors only, add scroll-timeline-attachment as described in the issue (Issue #7759: Broader scope of scroll timelines)
• Resolved: Collapse keyframes with same specified offset to the earlier one, then pull percentage-only keyframes to the front and sort them (Issue #8507: Keyframe ordering and ordering requirements)
• Resolved: Accept proposal in the issue (Issue #8405: animation-range vs animation-duration)
• Resolved: Scroll overlap range is in addition to scroll-padding, view-timeline-inset should have an initial value of auto (Issue #7747: Consider initial value of auto for view-timeline-inset)
• Resolved: animation-range’s initial value is the keyword “normal” (Issue #8406: Naming the initial value of animation-range)
• Resolved: For printing/paged, root is considered fully in view (scroll timelines on it are inactive) (Issue #8226: Define scroll linked animation behavior in printing documents)
• Resolved: Percentages outside the 0-100 range are valid in progress percentages (Issue #8552: Clarify that progress percentages must be between 0% and 100%)
• Resolved: Make `percentage` optional in animation-range-start/end, defaulting to 0%/100% (Issue #8438: Allow optional `percentage` in `animation-range-*`)
• Resolved: When specifying “animation-range: foo X%”, set the -range-end to “foo 100%” (staying in same phase, just setting to end) (Issue #8438)
• Resolved: SLA uses logical interpretations of scrolling (rather than scrollLeft/Top always) (Issue #7752: ViewTimeline values of startOffset/endOffset in RTL writing mode)
• Resolved: Pending Brian’s potential objections, go with `getCurrentTime(rangeName?)` (Issue #8201: Animation.getCurrentTime is easily confused with Animation.currentTime)
• Resolved: SLA does do flat-tree lookup for nearest ancestor scroller, spec will be clarified (Issue #8192: Timeline lookup should probably not use flat tree)
• Resolved: New features are not added to the animation shorthand (for now), they’re just reset (Issue #8054: Animation short-hand support for new properties)
• Resolved: Merge keyframes if their *specified* offsets match, don’t try to merge based on computed (Issue #8487: Avoid merging named timeline range keyframes which compute to the same offset)

CSS Overflow

• Resolved: Republish Overflow 3

Full Meeting Minutes

« Previous article Next article »