Minutes Telecon 2024-08-14
- Resolved: Add 1 more calc-size edit in, then issue first working draft of css-values-5
- Resolved: Add ChrisL and TabAtkins for easing level 2 and publish FWD (Issue #10688: Time for FPWD)
- There was a lot of discussion and thought about if tooltips are worth solving in issue #9236. There wasn’t a clear yes or no decided on the call, however a lot of good points were raised that needed further discussion. Some of the questions/comments were:
- Specific delays might be better than named values
- Different delays based on modality, hover vs touch
- If focus delay should be zero or if tabbing should have a different behavior
- Should there be a pseudo class for first tooltip open
- Resolved: Edit in what’s described in Tab’s last comment (Issue #10179: Should :not(foo) match the host of the shadow tree?)
- Resolved: :host:has() can match, :has() can’t (Issue #10693: Should `:host:has()` match?)
Full Meeting Minutes
OpenUI-WHATWG/HTML-CSSWG Meeting Minutes 2024-08-08
OpenUI-WHATWG/HTML-CSSWG meeting
CSS UI
- Resolved: Pseudo-element selectors apply only to the UA-provided elements in a particular role (Issue #10462: Pseudo-elements for stylable select)
Form Controls
- The group discussed the proposal to have incremental opt in for elements with pickers using ::picker pseudo (Issue #10440: Styling form control pickers).
- Several folks spoke about author needs in this space. Having to set several properties increases the burden on authors, especially at smaller firms with limited resources. However, there has not been specific research on this topic so there could be room to learn more about author needs and wants.
- Additional to the author needs, there was also concern expressed that if the first opt-in releases aren’t scoped to specific element types, authors would use a broad opt-in and it would lead to compat problems when functionality expands.
- There was broad agreement that appearance:base is the north star that the group should be working toward, though some disagreement on how long/hard that will be to achieve.
- As the call concluded, there was a proposal to ship appearance:base-select just for selects as an increment and then ship appearance:base for everything. There was support expressed, but the call ran out of time for further discussion.
Full Meeting Minutes
Minutes Telecon 2024-08-07
- Resolved: Name of properties are text-box-edge and text-box-trim (Issue #10675: Naming text-box-trim et al.)
- Resolved: Use trim-start and trim-end instead of start and end (Issue #10675)
- Resolved: The value “trim-both” for property “text-box-trim” (Issue #10675)
- Resolved: “text-box” shorthand with value “normal” set the longhands default (Issue #10675)
- Resolved: Republish as CSS Inline WD
- Resolved: “normal” value for “line-break” must not break between regular kana and small kana (Issue #10363: Japanese small kana and `line-break: normal`)
- Resolved: Allow (but don’t require) repositioning or fading (Issue #10418: Position of the text-overflow ellipsis)
- Resolved: color-layers([`blend-mode`, ]? `color`#) (Issue #8431: Add color functions for some (or all) compositing/blending operations)
Full Meeting Minutes
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