Minutes Telecon 2025-05-14
- Resolved: Change stretch alignment case to allow the size to stretch when the normal alignment case allows stretching (Issue #11195: Absolute positioning – Is the new inset & auto-size behaviour web-compatible?)
- Resolved: Shorthands serialize using the resolved value of the individual longhands (Issue #11382: Do shorthands serialize with the resolved value of their longhands?)
- Resolved: Start defining a `grid-collapse` property (Issue #5813: grid-gap is still taking up space when an element defined in grid-template-area is not on the page)
- Resolved: Values of `justify-self` other than normal or stretch treat the automatic size as fit-content, just like in flex/grid (Issue #12102: Clarify how `justify-self` affects automatic size of block-level box)
- Resolved: Auto margins do not prevent justify-self from imposing fit-content (Issue #12102)
- Resolved: Anonymous block boxes always stretch (go with option 1) (Issue #11461: `justify-items` and anonymous block boxes)
Full Meeting Minutes
Update on CSS Anchor Positioning
The CSS Anchor Positioning Module Level 1 has come a long way since its First Public Working Draft in 2023, with significant shifts to the syntax of the anchor() function, the introduction of the position-area property, the redesign of position-fallback/@position-fallback into the position-try property and at-rule, the addition of anchor-scope and position-visibility, and many adjustments and improvements to the underlying algorithms, resulting in a more powerful and easier-to-use technology.
Special thanks go to Google, for spearheading the initial specification effort and working through multiple prototypes to identify and overcome technical hurdles; to Apple, for proposing and incorporating conceptual and interface changes and additions that brought this feature to the level of usability and system integration we expect for CSS; and to our creative Invited Expert Roman Komarov, who kept experimenting and pushing the edges of what was possible while reporting issues along the way, prompting myriad improvements to the feature. This kind of early engagement from authors on feature design paid off hugely in the development of CSS Grid Layout, and again here for CSS Anchor Positioning.
Our most recent Working Draft incorporates some relatively minor changes, showing that the draft is becoming increasingly stable, even as issues remain.
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-anchor-position-1]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
We are particularly interested in comments and suggestions on improving the accessibility guidance, and welcome examples of best practices that could be incorporated into the specification. Feel free to comment on issues (or file new ones) in the CSSWG repo, and note additional discussion in the WHATWG HTML repo and in the html-aam repo which you can contribute to.
Minutes Telecon 2025-05-07
- Resolved: Use “constrained” for the middle value (Issue #11698: New values for dynamic-range-limit property)
- Resolved: Accept the proposal in the issue (Issue #12031: Should highlightsFromPoint also return ranges under the hit point?)
- The possible models to address issue #12119 (How should AnimationTrigger work?) were reviewed and folks were asked to add their thoughts to the github.
- Resolved: Specify that ‘opacity’ has no effect on hit-testing (Issue #11339: Impact of masks on hit-testing needs to be specified)
- Resolved: Specify that ‘mask’ has no effect on hit-testing (Issue #11339)
- Resolved: Define some way for clip-path to derive a path from an image, similar to shape-outside. Details TBD (Issue #11339)
- There wasn’t consensus on if the proposal to address issue #3720 (Add a ‘hairline’ border-width value) should be a new unit or a new keyword.
Full Meeting Minutes
Minutes Telecon 2025-04-30
- Resolved: Publish FPWD of CSS Custom Functions
- Resolved: Copy linear gradients timing details into the linear function (Issue #11211: Resolving curves not available at parse time)
- Resolved: Remove the event (Issue #7693: No event to track window position)
- Resolved: Add scrollParent to the spec (Issue #1522: Consider adding Element.scrollParent)
- Resolved: All CSS-defined functions serialize to lowercase (unless otherwise defined), just like CSS-defined identifiers (Issue #11556: Serializing of functions)
Full Meeting Minutes
Minutes Telecon 2025-04-23
- Resolved: Have sibling-index() and sibling-count() to default to DOM tree (Issue #9562: Allow specifying flat vs light tree in `sibling-index()` and `sibling-count()`)
- Resolved: Adopt spec text as quoted, i.e. no change to spec. (Issue #11195: Absolute positioning – Is the new inset & auto-size behaviour web-compatible?)
- The proposal for issue #11926 (Nested ::view-transition-group should have a container pseudo) was to add new new container. Through discussion there were initially questions about expected behavior and if the complexity was worthwhile. More examples will be added to the issue including the broader context of what use cases this would impact.
Full Meeting Minutes
Minutes Telecon 2025-04-16
- Though issue #10674 (UAs inconsistent in how OS font settings affect the default font-size `medium`) was brought for a resolution on the name, through conversation the group discovered a lack of clarity around what are the different behaviors across browsers and devices. In addition to names, it was suggested something like an explainer be created that lays out the various behavior combinations and expected results to help guide understanding.
- Resolved: Working title is preferred-text-something (Issue #10674)
- Resolved: Working title is preferred-text-scale, continue work on defining how it interacts with all the zooms and things (Issue #10674)
Full Meeting Minutes
Minutes Color HDR Breakout 2025-04-09
Color HDR Breakout
- Require `H2 >= H1`? (Issue #11787)
- Resolved: Require strict inequality for H1 and H2
- 2.4 “two dynamic-range-limit-mix values” should be “two or more …” (Issue #11694)
- Resolved: Allow single value, well defined
- Auto value of dynamic-range-limit (Issue #11558)
- There was general agreement to add an auto value, but not yet agreement on how it should behave. Folks will keep thinking about the behavior and come back to this issue.
Full Meeting Minutes
CSS Grid: Level 1 & 2 updated, Level 3 (masonry layout) reworked
The CSS Working Group has published an updated drafts of all three levels of CSS Grid: CSS Grid Layout Level 1, CSS Grid Layout Level 2, and CSS Grid Layout Level 3. The update to Levels 1 & 2 are largely adjustments to the core layout algorithm (see changes); the update to Level 3 (which was published in early February) resolves a few key debates in masonry layout and opens up some additional design questions (see overview).
The early drafts of CSS Grid Level 3 contained two competing proposals. The February update incorporates the CSS Working Group’s resolution to re-use the grid-* properties for track templating and item placement, and, prompted by feedback from W3C’s Technical Architecture Group (TAG), sketches out a new direction for controlling layout flow using a unified set of properties that would work across both Flex and Grid layout. There are still many unsettled debates for in this model, but also excitement about the possibilities that have been opened up.
The CSS Working Group invites 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-grid]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Color HDR Breakout 2025-03-26
Color HDR Breakout
- Initial value of `dynamic-range-limit` (Issue #11429)
- If the default is constrained originally it can be fixed later, but no-limit would need to stay in place. However, there are concerns about SDR being too strong a presence and holding back HDR growth.
- There is more research needed to reach a decision. smfr will check if the default for video could be constrained and ccameron will check what’s possible to share about limiting HDR on ad networks.
- Add target HDR headroom to `CanvasRenderingContext2D` (WHATWG Issue #11165)
- The group reviewed the proposal, available here.
Full Meeting Minutes
Minutes Telecon 2025-03-26
- Resolved: When aspect-ratio is non-initial, then min-size:auto serializes as ‘auto’ in gCS() (rather than being censored to 0) (Issue #11716: Resolved value of min size properties doesn’t round-trip)
- Resolved: Accept the proposal for changing random caching as stated in the issue (Issue #11742: Maybe min, max and step should not be part of the random-caching-key)
- Resolved: Go with element-shared for now, keep renaming issue open because many people are unhappy with it (Issue #11742)
- Resolved: Initial value of reading-flow is “normal” (Issue #11396: Initial value of `reading-flow`)
- Resolved: Add ‘source-order’ value applying also to block containers (Issue #11396)
- Resolved: No change to the default behavior for reading-flow and dense grid for now, because there’s no proposal (Issue #11396)
- The question as to if reading-order should work by default that is included in issue #11396 will remain open while Apple consults their accessibility team.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: