Minutes Telecon 2024-07-31
- Resolved: Remove grid-template properties from the list of properties that calc-size is valid for and that interpolate-size works on (Issue #10618: should calc-size() and interpolate-size apply to grid-template-rows and grid-template-columns?)
- Resolved: Throw on insertRule only when there are no valid declarations. Do not throw otherwise (Issue #10520: Error behavior for insertRule with declaration blocks)
- Resolved: Allowing mixed track sizing, as long as the algorithm does not allow position-dependent effects (Issue #10053: Intrinsic track sizing algorithm for masonry can go exponential in complexity)
- Resolved: Add a note about the grouping optimization and baseline handling (Issue #10053)
- Resolved: Shapes Level 1 is modified to say that shape-outside takes all `basic-shape` (Issue #9728: Clarify which `basic-shape` are valid in `shape-*`)
- Resolved: Publish a new CRD of Shapes 1 with this [above] change (and whatever else is already in since last publication)
- Resolved: Accept Noam’s PR (switch to `using`, allow reordering grammar) (Issue #5841: Minor comments on shape())
Full Meeting Minutes
OpenUI-WHATWG/HTML-CSSWG meeting 2024-07-25
OpenUI-WHATWG/HTML-CSSWG meeting
How to implement and shape API for `selectedoption` element for `select`
- Resolved: Move forward with the light dom cloning API shape and discuss timing in the issue
Popover Topics
- There was strong use cases to support the need to solve especially for the tooltip case, though also acknowledging this will be challenging on touch interfaces.
- Several people clarified that, though we’ve been just saying tooltip, they had both a rich and a basic tooltip in mind that would have somewhat different behaviors/needs.
- Concerns were also raised if this was the right ux to expose information. Some folks believed it was, but others will have conversations with design teams to form an opinion.
- Discussion will resume in a few weeks after folks have had a chance to think more with their internal teams.
CSS UI
- There was a brief introduction to the proposal to have pseudo elements to target the fallback element and the concern that we need to use something that doesn’t expose the shadow parts. Time ran out before the group could discuss further so conversation will continue on the issue. (Issue #10462: Pseudo-elements for stylable select)
Full Meeting Minutes
Minutes Telecon 2024-07-24
- Resolved: container-type does not force layout containment, but does force an independent formatting context (Issue #10544: Weaker form of layout containment for container queries)
- Resolved: UA is allowed to capture old elements in low resolution if they are off-screen (Issue #8282: Ignore offscreen elements from participating in transitions)
- The group discussed the possibility of using ‘auto’ for issue #8320 (view-transition-name determined by element). The focus was on the ability to interact with this ‘auto’ element and potentially using an ID to allow interaction. Good progress was made on the call and discussion will return to github for further refinement.
- Resolved: Adopt masking requirement for CSSWG meeting room Th/Fri at TPAC plus daily testing as documented in the wiki
Full Meeting Minutes
Minutes Telecon 2024-07-17
- Resolved: Publish new WD of Conditional 5 (Issue #10433: Reorganizing the Containment specs)
- Resolved: When the caret is past the end of a line, attempt to show the caret even if it overflow, with any necessary clipping behavior we end up needing to be specified later. (Issue #10289: caret-shape: block/underscore and overflow)
- Resolved: Specify the -webkit-* values for text-align in the Compat spec (Issue #10388: Specify HTML alignment as text-align: -webkit-{left,right,center})
- Resolved: Use `named-feature()` as the function name (Issue #9875: Choose names for keyword-based feature queries in @supports and names for initial set of queries)
- Resolved: Call the keyword `align-content-on-display-block` (Issue #9875)
- Resolved: Delete FontFaceSet constructor from the spec (Issue #10390: Remove the FontFaceSet constructor?)
- Resolved: Move the missing position fixup to computed value time (Issue #10374: Gradient interpolation doesn’t specify how to handle positionless stops at computed-value time)
- The group wasn’t ready to close issue #3080 (Do we need :focus-visible-within?) yet, but agreed to remove it from call agendas until there is more discussion in the issue as to if the use case can be covered by shadow dom or not.
- Resolved: Add .width and .height as doubles to the layout viewport interface (Issue #5260: No way to access the viewport size without losing precision)
Full Meeting Minutes
Minutes Telecon 2024-07-10
- Resolved: Put this proposal into css-mediaqueries-5 (Issue #6517: Script control of (prefers-*) queries)
- Resolved: Add lwarlow as an editor for mediaqueries-5
- Resolved: Change inset-area back to position-area (Issue #10209: Bikeshed name of `inset-area`)
- Resolved: Drop the next value of masonry auto flow (Issue #10232: Drop next value of masonry-auto-flow)
- Resolved: Drop masonry-auto-flow (Issue #10231: merge masonry-auto-flow into grid-auto-flow?)
- Resolved: Cursor property applies to ::marker pseudo (Issue #6203: The `cursor` property should apply to `::marker`s)
Full Meeting Minutes
Minutes Telecon 2024-07-03
- Resolved: Bare declarations in a scoped rule apply to the scoped root and add no specificity (Issue #10431: @scope as a nested grouping rule and CSSNestedDeclarations)
- Resolved: Reverse the previous resolution and not serialize implicit :scope pseudos (Issue #9621: Always serialize the implicit `:scope`?)
- Resolved: Allow bare declarations in a top level scope rule (Issue #10389: Allow declarations directly in @scope?)
- Resolved: “Like most operations in CSS besides selector matching, features in this specification operate over the flattened element tree.” goes to anchor positioning spec (Issue #10325: Flat tree vs. anchor-scope)
- Resolved: Transparent colors in the thumb are transparent towards the track, and transparent colors in the track are transparent towards the background; transparency in those colors is not generalized to the entirety of the scrollbar (Issue #9853: What do (semi) transparent colors mean for scrollbar-color)
Full Meeting Minutes
OpenUI-WHATWG/HTML-CSSWG Meeting 2024-06-27
CSS UI
- Resolved: `select` internals can be represented with shadow DOM (but shadow DOM support is not required as long as the behavior is the same) (CSS Issue #10380: DOM/Box structure for appearance:base-select)
- Resolved: Accept shadow dom structure as proposed initial comment in the issue, except for the svg part and naming of pseudo elements. Issues to be opened for those (CSS Issue #10380)
- Resolved: User agent styles can depend on appearance:base. Aim for eventual interoperability across all values of the property (CSS Issue #10028: Changing UA styles based on the computed value of the appearance property)
Anchor Positioning
- Resolved: popovertarget creates an implicit anchor element reference (WHATWG PR #9144: Add anchor attribute)
- Resolved: Develop HTML markup to represent semantic anchoring relationships (and which also set the implicit anchor element) for non-popover use cases (WHATWG PR #9144)
- Resolved: It would be a good idea to add an imperative way to set invoker relationships between popovers (WHATWG PR #9144)
Full Meeting Minutes
Minutes Telecon 2024-06-26
- There still is not general agreement on an overall approach to shorthandifying properties (Issue #8398: How safe is it really to shorthandify properties?). Some group members are proposing a general guidance against shorthandifying well-established properties, but others preferred investigating mitigation strategies to ensure shorthandification was still possible when justified.
- Resolved: Switch block-step-insert margin and padding values to margin-box | padding-box and add content-box, with attention to impact on aspect-ratio (Issue #10486: Add `content-box` to `block-step-insert` so authors can have content grow instead of adding space)
- Resolved: Rename position-try-options to position-try-fallbacks (Issue #10395: Rename `position-try-options` to `position-try-fallbacks`)
- Resolved: ::view-transition-old` renders new live image (if available) if old element is offscreen at capture time (Issue #8282: Ignore offscreen elements from participating in transitions)
- Resolved: The geometry animation on the `::view-transition-group` pseudo is same as before (Issue #8282)
- Resolved: No change to specification (Issue #8040: Containing block of dialog fixed position children)
- Resolved: Use Chrome/Firefox behavior (Issue #10268: Zoom and container queries)
- florian introduced a possible solution to issue #5648 (contain:size shouldn’t fragment as monolithic), but there wasn’t strong implementor interest. The group ran out of time on the call before they could discuss the use case further, though.
Full Meeting Minutes
Minutes Telecon 2024-05-29
- Resolved: 1. Introduce a CSSNestedDeclarations object inheriting from CSSRule and having a .style accessor, and use that to represent the declaration lists in a CSSStyleRule. It serializes as a raw declaration list. 2. Extend .insertRule() to parse declarations (or, if Web-compat requires, add .insertDeclarations()) into a CSSNestedDeclarations Object. 3. Open a new issue wrt the first declarations block. (Issue #10234: Design of `@nest` rule)
- Resolved: anchor() arguments can be reordered (Issue #10317: anchor() arguments should be reorderable)
- Resolved: Make anchor-size() default to the keyword matching the axis of the property it’s used in (Issue #10318: anchor-size() argument should be optional)
- Resolved: Accept proposal in 10316 but don’t change normal behavior when not using inset-area (Issue #10316: Should alignment safety consider the containing block?)
- Resolved: position-try: none | [ [dashed-ident || try-tactic] | inset-area ] i.e. remove the inset-area() (Issue #10320: position-try: inset-area() does not reflect CSSWG resolution)
Full Meeting Minutes
OpenUI-WHATWG/HTML-CSSWG Meeting 2024-05-23
OpenUI-WHATWG/HTML-CSSWG Meeting
CSS UI- appearance: base to enable interoperable styling of controls/components (Issue #5998)
- The group resumed the conversation to reach a decision as to if the best approach to styling of controls/components is opting in via a CSS property
- Anne shared a presentation outlining webkit’s vision for appearance:base to ground the group in a common purpose and language.
- The biggest concern with the presentation was the approach to pickers
- Pickers were presented as being specced later than other elements and some folks thought it needed to be tackled earlier.
- The feature rollout for pickers was discussed and it was clarified that the proposal intended a pseudo element to allow detection.
- A separate issue will be opened to address pickers so this discussion can continue.
- There was discussion around the difference in implementation between appearance:none and appearance:base to avoid some compat problems.
- Achieving the full vision may require HTML work, but there was agreement that the opt-in should be in CSS.
- Resolved: Use css to opt into styleable mode
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: