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
Minutes Telecon 2024-05-22
- Resolved: Close the issue, adding a note to the ink overflow definition about platform and rendering differences (Issue #8649: Specify extent of ink overflow)
- Resolved: Leave open, bring back in the upcoming F2F (Issue #7767: Add a meta viewport parameter to control ICB layout behavior for interactive overlays)
- Resolved: Change minimum size of flex items to be the larger of min-intrinsic and transferred size (Issue #6794: Change content-size suggestion to min-intrinsic instead of min-content?)
- There was concern that the proposal in issue #10315 (Alignment shouldn’t interfere with sizing) would cause poor behavior in a majority of cases. However, the proposal in issue #10316 (Should alignment safety consider the containing block?) could address that concern. The group will return to issue #10315 later after folks have had a chance to read and discuss issue #10316.
Full Meeting Minutes
Minutes OpenUI-WHATWG/HTML-CSSWG Meeting 2024-05-08
Presentation on styleable `select`
- jarhar gave a presentation on the background and use cases for a styleable `select` as an introduction to other agenda topics for the meeting. The slides are available here.
CSS UI- appearance: base to enable interoperable styling of controls/components
- The discussion for issue #5998 was centered on answering some questions and re-grounding everyone in the history of this topic since conversations had previously happened across groups separately.
- Some of the historic and current doubts raised were around future compatibility and the property being too specific as well as doubts around accessibility and ergonomics. Many of these concerns, though not easy, have been thought through and addressed in the proposed future state.
- The next step is to see if there is agreement at a conceptual level to add this to CSS with details on exact properties and behavior to be defined in a separate issue. To that end, a summary comment will be added to github for further discussion offline before the next meeting.
Full Meeting Minutes
Minutes Telecon 2024-05-15
- Resolved: Make position a shorthand of position-anchor and a new position-type property. The shorthand resets both (Issue #10321: `position-anchor` should be defined as a longhand of `position`)
- Resolved: Fix definition of revert-layer’s behavior to match the general behavior elsewhere (Issue #10319: revert-layer should only revert the Position Fallback Origin)
- Resolved: Rename implicit to auto in position-anchor (Issue #10312: Initial value of `position-anchor` should be `auto` not `implicit`)
- Resolved: Drop the keyword from the anchor() function (Issue #10312)
- Resolved: If inset-area spans two tracks we’ll align toward the missing track instead of centering (Issue #10313: Default alignments for inset areas are wrong)
- Resolved: Container queries and units use the flat tree (Issue #5984: CQ vs shadow boundaries)
- There was general agreement on having an ‘auto’-like solution and an ‘attr()’-like solution for issue #8320 (view-transition-name determined by element) but not yet agreement on the details for the approach. Discussion will return to github to draft up a more concrete proposal.
Full Meeting Minutes
Minutes Telecon 2024-05-08
- Resolved: view-transition-name lookup is tree-scoped (Issue #10145: Should view transition names be tree scoped?)
- While discussing issue #9839 (Handle startVT for offscreen iframes), a new proposal came up to start an offscreen iframe animation with a negative start delay so that it could begin to animate when it appears without having to do a lot of work while it’s offscreen. There wasn’t time on the call to think through the potential upsides and downsides to this approach so discussion will return to github.
- Resolved: ::view-transition pseudo is the last child of its originating element, after everything else including other pseudo-elements (Issue #9588: Clarify ordering of `::view-transition` with other tree-abiding pseudo-elements)
- Resolved: Animation to/from keyword sizes requires an opt-in, so by default only get transition if at least one side gets calc-size() (Issue #626: Transition to height (or width) “auto”)
Full Meeting Minutes
Minutes Telecon 2024-05-01
- Resolved: Dispatch scroll snap events on pseudo elements by targeting the ultimate originating element (Issue #10175: Should pseudo-elements show up as null SnapEvent.snapTargetBlock/Inline)
- Resolved: Snap events targeting the document bubble in the same way scroll events do (Issue #10173: Should snap events fired at the document bubble?)
- Resolved: scrollsnapchanging and scrollsnapchange (Issue #9697: Use present tense for snap event names)
- Resolved: Add ::search-text, using :current to distinguish currently-focused match, mark as optional to implement (Issue #10212: Single highlight pseudo for find-in-page?)
- Resolved: ::search-text paints directly above or directly below ::selection (up to UA) (Issue #10213: painting order of find-in-page highlights)
Full Meeting Minutes
Minutes Telecon 2024-04-24
- jensimmons presented an overview of the proposal for issue #9041 (Alternate masonry path forward) and an accompanying demo to add clarity
- The Google & Edge implementors were concerned that the current proposal would not be implementable because the algorithm would cause exponential behavior in some cases and proposed some restrictions to prevent it (full details in this comment)
- Several folks expressed concern with including this in Grid since, though they have similarity, understanding masonry in a grid context would limit what masonry could do. On the other hand, authors could want to switch between grid and masonry at different breakpoints which would argue for keeping them together.
- Discussion will continue on github to allow folks time to think about and discuss the various ideas raised on the call.
- Resolved: `none` is preserved in calculations involving CSS math functions (Issue #10211: Clarify that `none` is preserved in calculations)
- Resolved: When interpolating between two none-containing values, the result is a calc-mix() expression preserving the `none` keywords in both values (Issue #10211)
Full Meeting Minutes
Minutes Text Breakout 2024-04-24
- Resolved: Start work on middle ellipsis in css-overflow-4 (Issue #3937: Ellipsizing of text in middle of string)
- Resolved: Number of lines can change if it’s 6+ lines being balanced, and note that this is about line breaks not content height shifts (Issue #10186: Should text-wrap-style:balance be allowed to affect the block height?)
- Resolved: Clamp, then balance (Issue #9310: Interaction of `text-wrap: balance` and `(-webkit-)line-clamp`)
- The group was poised to resolve on the proposal within issue #10073 (Breaks within implicit bases is not Web-compatible) however there were concerns about performance and not enough time to address them so discussion will return to the issue.
Full Meeting Minutes
Minutes Telecon 2024-04-17
- Issue #8738: Figure out whether we’re fine with “shifting up” bare declarations after rules-
- TabAtkins introduced the proposal for issue #8738 (Figure out whether we’re fine with “shifting up” bare declarations after rules) and proposed moving serialization into a separate issue
- There were some concerns raised about author confusion given that it’s easy to make a small change that would alter behavior.
- The proposal was viewed as an improvement over the current spec text and there was a desire to make a change now before the current spec text becomes relied upon by authors.
- The group discussed the likelihood of this being used by authors and the value of having it as something an author (especially in a tooling use case) could access vs the value of having well-defined and predictable magic.
- Though there was some pushback to magic, the principle of taking the least user-facing approach had wide agreement.
- Resolved: Tab specs @nest, with a note about @nest rules as a usable syntactic construct being something we might want to get rid of
Full Meeting Minutes
Minutes Telecon 2024-03-27
- Resolved: We will use shaped edge and unshaped edge (Issue #5132: How to refer to the corner-shaped padding/border/content edges)
- Resolved: Editorial update to level 3 box rec
- Resolved: View Transitions level 2 to public working draft (Issue #10096: FPWD for CSS View Transitions L2)
- Resolved: Use FrozenArray for CSS OM. VT typeset which is setlike for types attribute. Keep sequence of strings for svt as is. (Issue #10114: Data type for types in script APIs)
- Resolved: Don’t deduplicate values in reflections (Issue #10114)
- Resolved: Don’t drop invalid values in reflections (Issue #10114)
- Resolved: Make * optional if you are using a class (Issue #9874: Consider allowing `::view-transition-group(.class)` without *)
- Resolved: All scroll containers default to unsafe alignment (not actually unsafe on scroll container) (Issue #10008: Default safety of scroll containers)
- Oriol introduced proposed syntax to specify the agreed upon behavior for list-time nesting in issue #9076 (list-item counter nesting is confusing). There were questions on handling defaults and if the property should inherit, but the group didn’t have time to discuss further on the call so conversation will return to github.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: