Minutes Telecon 2025-03-05
- A few folks expressed interest in helping to address issue #11775 (Index of local font issues: fingerprinting, I18n, privacy) but had limited capacity. They will reach out to team members to see if they can find folks with capacity to assist. Additionally, ChrisL and astearns will work on addressing suggestions sent privately and furthering discussion on the issue.
- Resolved: Rename string keyword to raw-string (Issue #11645: Distinction between `attr(foo type(‘string’))` and `attr(foo string)` is too subtle)
- Resolved: Default styling for scroll markers will match default styling for links. Default styling for scroll buttons will match default styling for buttons (and appearance will apply accordingly). (Issue #10935: Default UA styles for scroll markers and scroll buttons)
- Resolved: Add a source-order value to reading-flow (Issue #11208: reading-flow and mix of auto-flow and explicit items)
- Resolved: reading-flow: source-order works on block containers. reading-order applies to block-level boxes, and not to inline-level boxes (Issue #11208)
Full Meeting Minutes
Minutes Color HDR Breakout 2025-02-26
Color HDR Breakout
- Resolved: Remove the sentence in spec that says if sum is zero, treat as invalid; possibly add new prose about splitting the percentage, and update tests (Issue #11678: How should checking for percentages summing to 0 work in dynamic-range-limit-mix() when calc() is used?)
- Resolved: Modify spec text as discussed, to try and flesh out if there are blocking compositor issues in implementations; possibly add an appendix of test cases and blocking issues with platform limitations (Issue #11037: How should multiple layered elements with different `dynamic-range-limit` values behave?)
- The group discussed issue #11704 (Add permission policy (or other mechanism) to irreversibly limit EDR) and what user and author expectations would be. There is a need to dive further into expectations and concerns that this needs to be addressed soon since HDR is starting to ship.
Full Meeting Minutes
Minutes Telecon 2025-02-26
- Resolved: Accept the general approach, change map naming to scale for now, iterate on syntax later (Issue #6245: Interpolate values between breakpoints)
- The group reviewed the proposed solution for issue #11408 (Do collapsed tracks also shrink the table wrapper box or only the table grid box?). The proposal made sense and was in the right direction, but there was a request to think more about handling wrapper and grid box sizes to see if there was a more expected outcome that could be achieved. Discussion will continue on github.
- Resolved: Overflow applies to the wrapper box (Issue #10881: Does `overflow` apply to table-wrapper or table-grid? css-tables contradicts CSSWG resolution)
Full Meeting Minutes
Minutes Telecon 2025-02-19
- Resolved: Publish Snapshot 2024 from the current draft, as a Group Note (Issue #11696: Finish up CSS Snapshot 2024)
- Resolved: block-step-size inherits, and does not activate step sizing (Issue #1902: Inherit block-step-size)
- Resolved: Add a new “none” initial value to block-step-align; all other values turn on step sizing (Issue #1902)
- Resolved: Try option 2 [use the scrollIntoView() position of the non-skipped ancestor of the marker for determining when the marker is active] (Issue #11705: Should ::scroll-marker pseudo-elements within skipped content-visibility: auto elements be discovered?)
- Resolved: Specify this new parsing behavior for all substitution functions, and some sort of spread-like thing (Issue #11500: Short-circuit if() evaluation)
- There wasn’t time to discuss all the questions in issue #11208 (reading-flow and mix of auto-flow and explicit items). The group leaned toward having the ability to set a property which says reading-flow:`stick-with-source-order` to answer the first question.
Full Meeting Minutes
Minutes Sizing Breakout 2025-02-19
CSS Sizing Breakout
- Resolved: Fixed table layout is triggered except when inline-size is auto (Issue #10937: What sizing keywords allow fixed table mode?)
- Resolved: Accept proposal (Issue #11044: How does height: stretch interact with margin collapsing with parent)
- Resolved: See if implementations can match the spec and revisit issue later (Issue #11452: Nobody follows the spec about cyclic percentages in preferred&max sizing properties of replaced element)
- Resolved: min-size: stretch behaves as zero, max-size; stretch as infinity, when in an indefinite container (Issue #11006: Does indefinite `stretch` behave as automatic size or as initial value?)
Full Meeting Minutes
Minutes Color HDR Breakout 2025-02-12
- Resolved: Add current proposal as a note into the spec (Issue #11616: CSS syntax for HDR colors parameterized by headroom)
- Resolved:Change high to no-limit (Issue #11698: New values for dynamic-range-limit property)
- weinig will create a PR to clarify the language called out in issue #11672 (Clarification on the grammar / spec text for `dynamic-range-limit-mix()`)
Full Meeting Minutes
Minutes Telecon 2025-02-12
- Resolved: We use a caret approach. It’s part of the syntax and not part of the name. Weak/strong with the same name is ok (Issue #6323: Allow authors to explicitly place unlayered styles in the cascade layer order)
- Resolved: Strength is exposed in CSSOM, details tbd (Issue #6323)
- Solving issue #3720 (Add a ‘hairline’ border-width value) was supported by the team, but the proposal needed more details added.
- Resolved: shape() remains as-is, spec subset that is more tightly tied to SVG
path for a path() overload (Issue #10647: Overload `path()` for CSS-y SVG path syntax instead of taking up `shape()`)
- There wasn’t clear support for the proposal to address issue #10773 (Elements with content-visibility in new Document) by having the content-visibility:auto determination run again when there is an incoming viewport. Discussion to clarify the proposal and discuss alternatives will continue on the issue.
Full Meeting Minutes
Minutes Telecon 2025-01-22
- Resolved: Adopt safe-area-max-inset-* values (Issue #11019: Maximum safe area inset values to allow sliding bottom bar)
- Resolved: enum ScrollIntoViewContainer { “all”, “nearest” }, defaulting to `all`, expanding to element in the future if needed (Issue #9452: Option for scrollIntoView that doesn’t propagate to ancestors)
- Resolved: UAs MUST preserve user privacy (Issue #11151: Proposal: Update :visited language to state UAs must preserve user privacy)
- There wasn’t a strong preference between the two options for issue #9724 (What does the `white-space-collapse` apply to when white-space trimming/positioning) will be written up in advance of the F2F. This will allow the authors to gain feedback on ease of implementation before selecting one option.
- Resolved: Close no change (Issue #10831: `anchor()` Fallback type inconsistency vs WPT)
- The spring F2F will be April 15 to 17. There is a poll for dates for the summer F2F. Group members are asked to fill in their availability.
Full Meeting Minutes
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
Minutes Telecon 2025-01-15
- Resolved: :has-slotted should use the flattened tree to resolve if content is slotted or not. We could later discuss a different pseudo-class for the other behavior (Issue #6867: Pseudo-class to indicate when a slot has content)
- Resolved: Do NOT establish BFC for block-step-size with details on when the extra space gets added to the bottom only to be determined in future conversations (Issue #11325: `block-step-size` should not establish an independent formatting context)
- Resolved: Close no change (Issue #1902: Inherit block-step-size)
- ChrisL has already responded to some comments on the rechartering request (Issue #10671) and astearns will reply to the remaining one. ChrisL will draft up a proposal to address the concerns in Brave’s objection and have it for the working group to review shortly.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: