Minutes Telecon 2025-07-02
- Pseudo classes for the `interestfor` API (Issue #12154):
- Concerns were raised that `possible` my be cyclic; if it causes issue it may be dropped.
- There was no clear agreement on how `partial` will work, especially in a mobile context. Discussion will continue on github and `partial` will move to a separate issue to make discussions easier.
- Resolved: Publish css-borders-4 with the edits described [add an introduction and move the not ready for implementation to partial borders]
- Resolved: Allow shipping with no-autospace as initial value, continue discussing eventual default behavior (Issue #12386: Reconsider the initial value of the `text-autospace` property)
- Resolved: Republish the WD (Issue #6245)
- There were several concerns raised on issue #12132 (Using logical keywords in background-position shorthand with multiple backgrounds) around how to implement and how to cascade. There wasn’t time to dive in further during the call so group members were asked to add examples of how the concerns would manifest to the github issue.
Full Meeting Minutes
Minutes Scope Breakout 2025-07-02
- Resolved: Close no change (Issue #12418: Should/can relative selectors be allowed un-nested)
- The proposed resolution from the call for issue #9740 (`&` matching inside the `@scope`, and its interaction with `:scope`) was `& in @scope behaves as :where(:scope)`. However, there were a lot of options and a lot of opinions, including some not represented on the call. Therefore, the team will hold on resolving for one week to give folks a chance to review and provide input.
Full Meeting Minutes
Minutes Telecon 2025-06-25
- Resolved: Overconstrained insets return their used value prior to adjusting for the overconstraint (Issue #3059: Resolved value of over-constrained percentages in inset properties)
- Resolved: Make @page/size a legacy alias of @page-page-size, will get feedback from print formatters on this issue (Issue #11925: Consider making ‘size’ a legacy alias of a new descriptor (‘page-size’)?)
- Resolved: Accept the PR, `stretch` falls back to `flex-start`, not `safe flex-start` (Issue #11641: Should ‘align-content: stretch’ use ‘safe’ in the fallback value?)
- Resolved: Confirm that -webkit-line-clamp should become a shorthand of line-clamp (unless we run into compat issue) (Issue #10439: How do `-webkit-line-clamp` and `line-clamp` interact when both are specified?)
- Resolved: Remove the “hidden longhands” text for line-clamp’s longhands, just make them normal longhands (Issue #10439)
- Resolved: Change `safe` alignment on scroll containers to align towards the scroll origin side (rather than the `start` side) (Issue #11937: The `safe flex-start` fallback alignment for `justify-content:space-between` is actually unsafe)
- Resolved: Actually specify getBoxQuads(), matching Firefox behavior for now (Issue #10537: update description of getBoxQuads API)
- Resolved: Make animation-timing-function, -iteration-count, -direction, -play-state inherit in the VT tree (Issue #11546: Have the `-image-pair`, `-old`, and `-new` pseudos inherit `animation-timing-function`)
Full Meeting Minutes
Minutes CSS Pseudo Breakout 2025-06-25
CSS Pseudo Breakout
- Issue #12158 (Add a property to the `CSSPseudoElement` IDL interface to determine if a pseudo element “exists”) will return to the github issue to define per element and answer some questions raised on the call.
- Resolved: For a valid selector we will always return the CSSPseudoElement object (Issue #12159: What should `pseudo(type)` return for elements that can’t have pseudo elements?)
- Issue #12160 (Should non-tree-abiding pseudo elements have a separate IDL interface?) requires further thought about event listeners so will return to the issue.
- Issue #12163 (How to handle addEventListener on `CSSPseudoElement`?) will be brought up at the joint meeting with WHATWG to get additional input.
- There was general agreement to have a separate property that returns the full string for issue #12161 (Add a property to the `CSSPseudoElement` IDL interface to retrieve pseudo argument(s)) however there wasn’t enough time left on the call to agree on details and reach a resolution.
Full Meeting Minutes
Minutes Telecon 2025-06-18
- Resolved: In a flex container’s cross axis, stretch sizing keyword resolves initially against the container, then re-resolves against the line once the line’s size is determined (Issue #11784: It’s false that `stretch` size behaves as `stretch` alignment)
- Resolved: Accept oriol’s proposal (Issue #11805: Intrinsic contribution of `fit-content()` with cyclic percentages)
- Resolved: No change (Issue #12053: Where does the default aspect-ratio of a `video` come from?)
- Resolved: Progress clamps by default between 0 and 1; we’ll add unclamped keyword, or other keyword if folks have suggestions (Issue #11825: Should progress() functions clamp to 0-100%?)
- Resolved: Rename scroll-marker-contain to scroll-target-group (Issue #12191: Bikeshed scroll-marker-contain property name)
- Resolved: Add second value to scroll-marker-group as [ tabs | links ] (Issue #12122: Discrete versus navigation scroll marker mode)
- Resolved: Triggers are an external controller of the animation (Issue #12119: How should AnimationTrigger work?)
Full Meeting Minutes
Minutes Telecon 2025-06-11
- The editor’s draft of pointer-animations-1 was published. Review and issues are welcome.
- The proposal for styling differently based on fallback selected from @position-fallback was added to issue #8171 (Detecting active @position-fallback). There were some questions to refine it further and, when ready, it will be added to Anchor Position 2.
- Resolved: Add :target-before and :target-after (Issue #11600: Selecting ::scroll-marker based on relationship to scroll target)
- Resolved: Use the writing mode of the target element (Issue #11796: scrollIntoView spec text (“determine the scroll-into-view position”) disagrees with browser behavior on which writing-mode(s) to use to determine sides)
- Resolved: The option will be called bevel (Issue #12232: corner-shape `angle` vs `bevel`)
Full Meeting Minutes
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
![[Photo: group photo of the CSS working group in San Francisco]](https://cdn.statically.io/img/www.w3.org/Style/CSS/csswg-2016.jpg)
Contact: