Minutes Nesting Breakout 2023-04-05
- Resolved: Redefine CSSRuleList as ObservableArray (Issue #8350: Consider using ObservableArrayCSSRule instead of CSSRuleList)
- TabAtkins will file issue about CSSStyleDeclaration’s array upgrade
- Resolved: If naked property declarations inside @media become a thing, they are wrapped in a & {} rule (Issue #7850: CSSOM for nested media query rules)
- fremy or plinss will file issue about whether naked declarations get sorted to the top of the list or not
- Resolved: Close no change (Issue #7803: Nesting conditional rules)
- We will retain the current spec behavior for issue #8399 (Feature detection for nesting) which is the bare & supports strategy.
- The lookahead proved viable for issue #8249 (Problem with mixing properties and selectors). Discussion will continue on github as to the final decision between the provided options.
Full Meeting Minutes
Minutes Telecon 2023-03-29
- Resolved: Accept the CSSScopeRule design, with the three changes noted in the thread (Issue #8626: What is the desired shape of CSSScopeRule?)
- Resolved: Add break-spaces to white-space-collapse (Issue #3794: white-space:break-spaces is in level 3 but not level 4)
- Resolved: Accept the proposed addition to the ‘white-space’ grammar [addition is ‘white-space-collapse’ || ‘text-wrap’ || ‘white-space-trim’ as values for white-space shorthand] (Issue #5382: Multi‑value `white‑space` syntax proposal)
- Resolved: Snapshot raster is theoretically infinite. Snapshot has a “natural view box” of the snapshot element’s border box (giving the natural size). Object-view-box can change this view box (Issue #8597: Exposing ink overflow rect bounds to script)
- Resolved: Closed invalid, fixed by the #8597 resolution (Issue #8606: Clarify the size of snapshot when there are nested transitioning elements)
- Resolved: Add :popover-open pseudoclass, undefined popoverness from :open (Issue #8637: Introduce `:popover` pseudo class)
Full Meeting Minutes
Updated CSS Text Level 4: Refactored text-spacing and white-space Shorthands
The CSS Working Group has published an updated Working Draft of CSS Text Level 4. This module covers covers white space processing; line breaking; text spacing, justification, and alignment; and text transformation.
This update significantly refactors the text-spacing property, completes the refactoring of white-space into shorthands, and renames its text-space-* longhands back to white-space-*. Changes since the last Working Draft are detailed in the Changes section.
We encourage everyone to review the syntax and behaviors of these two shorthands and their longhands, since several implementations are currently in progress:
Please send feedback by either filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-text-4]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2023-03-22
CSS Cascade
- Resolved: Cascade proximity is weaker than specificity (Issue #6790: Strong vs weak scoping proximity)
- Resolved: The combinator is deferred (Issue #8628: Do we want to defer some or all of these scope extensions to level 7?)
- Resolved: The name will be @scope-siblings (Issue #7751: Handle sibling-proximity in @scope)
CSS Animations
- Resolved: Include `overlay` property with values of `auto` and `none` to position-4 with a note about concerns over extensibility (Issue #8189: Entry and exit animations for top-layer elements)
CSS Contain
- Resolved: Elements within a display:none subtree have no parents that container queries can access (Issue #8197: Container queries within display:none are difficult to implement)
- Resolved: Add a function for every container query unit that allows to reference a named container (Issue #7858: Reference named containers for cq units)
- Resolved: Style queries can accept properties in boolean context; false if matches initial value, true otherwise (Issue #8127: Allow container query style features to evaluate in a boolean?)
- It’s unclear if the questions in issue #7875 (`overflow: auto` incompatible with size containment and container queries) are covered in the spec and need clarification or if there are changes to be made to handle contain-intrinsic-size.
CSS Color
- Resolved: Allow out-of-gamut HSL and HWB colors (Issue #8444: Allow out-of-gamut HSL/HWB colors (previously “Move gamut mapping to a future spec”))
- Resolved: Change specification say browsers MUST use OKLab color interpolation for all colors, including legacy colors (Issue #7948: What if legacy colors *also* interpolated in Oklab by default?)
Full Meeting Minutes
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
Full Meeting Minutes
Minutes Telecon 2023-03-15
View Transitions
- Resolved: If an element if fragmented into more than one element, it does not participate in View Transitions (plus note that we want to do such things in the future) (Issue #8339: Capturing fragmented elements)
- Resolved: If an element is involved in a transition, the `view-transition-name` constraints are enforced during the transition (Issue #8548: Define the constraints which must be satisfied by a named element during the transition)
- Resolved: Conditions are checked per-frame; transition is skipped if other constraints are broken (Issue #8548)
- Resolved: The view transition fills the viewport and captures clicks (Issue #8278: UA CSS should size ::view-transition to 0x0)
- Resolved: Target pointer events to the document element (Issue #7797: User input should be ignored when rendering is suppressed)
- Resolved: User agent can limit rasterization for performance limitations, but must size the element as if it was fully rasterized (Issue #8561: Define behavior when capturing image for a large element)
- Resolved: Rasterization must cover at least the visible area of the viewport (Issue #8561)
- Further discussion is required to determine how to handle painting overflow in issue #8561. There needs to be a bit more understanding of both author expectations and fingerprinting implications.
Full Meeting Minutes
Minutes Telecon 2023-03-13
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.
Full Meeting Minutes
Minutes Telecon 2023-03-08
- Resolved: Proxy from drafts.csswg.org to github.io, and have github.io redirect to our server
- plinss will set up the proxy server. rachelandrew will work with MDN and TabAtkins will work with WHATWG to get URLs changed.
- Resolved: Inertness is determined by the base computed style for ‘display’, resulting in animations to ‘none’ being considered inert (Issue #8389: Interaction gotchas when delaying the effect of `display: none`)
- Resolved: In LTR-tb the top-left corner is the top-left corner of the top-left-most fragment of the first line, and the bottom and right edges are bottommost and rightmost edges of all the fragments. Directionality comes from the inline (Issue #8284: Containing block formed by fragmented inlines)
- Resolved: Move color at the end of the final-bg-layer grammar, to make it serialize as `none` (Issue #8496: Serialization of `background: none`)
Full Meeting Minutes
Minutes Telecon 2023-03-01
- The group was positive about the simplification proposed in FXTF Issue #363 (The description of contain flag in ray() function). They would like to make sure that folks who are expert in watch design are involved and then bring the issue back when the spec text is written.
- Resolved: Accept restrictions in this github comment with exception of :is and :where (Issue #8174: Add pseudo-class to establish before-change style for css-transitions on new elements)
- Resolved: Adopt this feature as overflow-bikeshed [name is to be decided later] (Issue #8361: Add method to prevent elements from contributing to scrollable overflow)
- Resolved: Accept this behavior for baseline-source:first|last (Issue #8214: baseline-source:first and overflow:hidden inline-boxes)
- Resolved: leading-trim: normal; >> text-box-trim: none; AND text-edge >> text-box-edge (Issue #8067: Naming Stuff)
- On the call there was a possible solution raised for issue #8286 (Making a stickypos in a scroller also see the viewport edges) to use overflow:clip so it’s explicitly not scrollable. Initial reaction was that that could work, but discussion will return to github to investigate further
Full Meeting Minutes
Minutes Scoping Breakout 2023-03-01
- Resolved: Close the issue as no-change (Issue #7943: change lower boundary keyword for @scope to “until”)
- Resolved: Accept clarifications for scoping selectors proposed by miriam (Issue #8377: Scoped selectors shouldn’t match the scope root unless explicitly requested with :scope?)
- Resolved: The specificity of the scope root is not applied to selectors from scoped rules (Issue #8500: The specificity of a scope rule)
- The examples and developer feedback for issue #6790 (Strong vs weak scoping proximity) were arguments for weak proximity. The group members looking for strong proximity are asked to add use cases into the spec over the next week so the working group can further discuss and reach a resolution.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: