Minutes Telecon 2025-06-04
- Resolved: Move shape() to css-shapes-1 and ask for wide review on that and maybe path() and add noamr as editor to css-shapes-1
- Resolved: When selecting a viable priority candidate (e.g. contenteditable), run the regular selection algorithm scoped to that element instead. (Issue #11748: anchoring within contenteditable elements)
- Resolved: Define shorthand interest-delay for interest-delay-start + interest-delay-end (Issue #9236: Add “show interest” and “lose interest” hover delays to CSS)
- Resolved: Add a normal keyword as initial value to match platform conventions (Issue #9236)
- Resolved: Start with single value, add a note about possibility of needing alternative values for e.g. keyboard/touch (Issue #9236)
- Resolved: Revert change to make all gradients interpolate in OKL by default (Issue #7948: What if gradients with legacy colors *also* interpolated in Oklab by default?)
Full Meeting Minutes
Open UI-WHATWG/HTML-CSSWG Meeting Notes 2025-05-29
OpenUI-WHATWG/HTML-CSSWG meeting
File upload control rendering should specify the button element to use (WHATWG Issue #11130)
- When discussing the file-selector-button there was discussion around if we should be seeking consistency for form control pseudos and, if yes, what direction should we be consistent.
- Generally it was agreed that consistency would be a good goal and that we should be consistent around element-backed. At the same time, file-selector-button was seen as a candidate to special case.
- Resolved: Remove the “element backed” line from CSS spec for :file-selector-button
Other hot topics
- The group discussed the problems with color and the wrapper uncovered during the color swatch implementation investigation. The initial lean was to continue down the path of removing the wrapper.
- Usage data is still being collected to determine the impact of changing what happens with multiple when you don’t have a size attribute.
Full Meeting Minutes
Minutes Telecon 2025-05-28
- Resolved: Start specifying element-scoped view transitions in view transitions L2 (Issue #9890: Element-scoped view transitions)
- Resolved: Add ::view-transition-group-children() (open to better names), and copy border-sizing properties to it (Issue #11926: Nested ::view-transition-group should have a container pseudo)
- Resolved: Scroll state queries against the root match the scroll state of the layout viewport (Issue #11542: Match scroll-state(scrollable) for root element on viewport)
- Resolved: Scroll state containment on root element blocks overflow/scroll-related propagation from the BODY element (Issue #11542)
- Resolved: Add corner-shape to the border-radius clause in outline definition (Issue #12194: Specify how `corner-shape` affects `outline`)
Full Meeting Minutes
Minutes Telecon 2025-05-21
- Resolved: Explicitly allow tree-counting functions in container queries (Issue #10982: Disallow mix/random/tree-counting functions in some contexts)
- Resolved: Working on scrolling queries (Issue #6400: Expose current scrolling direction)
- Resolved: Reduce all radii in order to avoid overlap of shapes (Issue #12098: Consider constraining radii for concave corner-shape when opposite corners overlap)
- There was some initial preferences toward the third option, add env(hairline), to resolve issue #3720 (Add a ‘hairline’ border-width value). Several questions were unresolved on the proposal at the end of the call time, so discussion will continue on github and a future call.
- The group will experiment with creating a scribe rota to help expedite the process of selecting a scribe each call. Group members interested in being on the rota can add their name to the wiki.
Full Meeting Minutes
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
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: