Minutes Telecon 2025-01-08
- Resolved: text-box-trim does not change height contribution of inline (Issue #10834: inline boxes and line-fit-edge vs text-box-trim/edge)
- fantasai will make a testcase for the above resolution and report back on WebKit/Chrome implementation status.
- Resolved: If text-box-trim reduces the effective height of the inline box compared to line-fit-edge, that amount is propagated as a negative margin (the same way as a specified negative margin is propagated) to inline descendants (Issue #10384)
- Resolved: Apply text-box-trim to a column box or spanner iff it is adjacent to the relevant edge (Issue #11363: text-box-trim and multi-column containers)
- There was discussion around the naming decision for issue #10975 (:local-link should have a more precise name) but no clear answer was discovered during the call. Discussion will continue on the issue to outline possibilities.
- Resolved: `:has-slotted` should match when the fallback content is not being displayed (Issue #6867: Pseudo-class to indicate when a slot has content)
- Resolved: Restrict ordering such that `to` or `by` would need to come first (Issue #10666: Order of points and control points in `shape()`)
Full Meeting Minutes
Minutes Telecon 2024-12-18
- There were multiple clarifying questions about the proposal in issue #11185 (select:hover and select:active styles).
- There is an exception for top layer in the proposal, but it wasn’t clear if that exception was enough to prevent breakage in menus. The carousel scroll-marker/group is not in the top layer and would still need some exception as well.
- Creating a CSS property was discussed as an alternative, though it could create loops so needed to be approached mindfully.
- Discussion will continue on the github issue.
- Resolved: Adopt ident() function into css-values-5 (Issue #9141: A way to dynamically construct custom-ident and dashed-ident values)
- Resolved: Use the `match-element` keyword for this and disallow it as a value in view-transitions-1 spec (Issue #10995: Allow an auto-generated `view-transition-name` that doesn’t default to ID)
- The proposal for issue #10834 (inline boxes and line-fit-edge vs text-box-trim/edge) was introduced for more discussion in the next meeting.
- Group members were requested to register for the next F2F if they’re planning on going.
Full Meeting Minutes
Minutes Telecon 2024-12-11
- Resolved: WG likes the logo and would like to officially endorse it, will investigate what that means (Issue #11193: Adoption of the logo created by the CSS Next CG)
- Resolved: FPWD of color hdr (Issue #11344: Time for FPWD)
- Resolved: FPWD of Display 4
- Resolved: FPWD of Overflow 5
- Resolved: FPWD of Multicol 2 (as a full spec, not diff)
- Resolved: scrollsnapchanging uses the targeted location for targeted scrolls, but does not predict the destination of momentum scrolling (uses the current scroll location instead) (Issue #10838: Should scrollsnapchanging target the currently visible element during flings)
- Resolved: `scroll-initial-target: none | nearest` (Issue #11173: scroll-start-target: auto doesn’t match general meaning of auto)
- Resolved: `overflow-clip-margin: content-box` applies to scrollable boxes (Issue #10745: Should overflow-clip-margin apply to scrollable boxes?)
- There was interest in addressing the use case in issue #10674 (UAs inconsistent in how OS font settings affect the default font-size `medium`) but the group ran out of time before they could reach agreement on the best approach. Discussion will continue on github.
Full Meeting Minutes
Minutes Open UI-WHATWG/HTML-CSSWG Joint Meeting 2024-12-05
OpenUI-WHATWG/HTML-CSSWG meeting
CSS UI
- Resolved: Have the same border radius for base appearance for selects and buttons, conditional on giving others not present a week to review. (issue #10857: UA stylesheet for appearance:base `select`)
- Resolved: Use transparent background color for base appearance selects, buttons, and inputs (Issue #10857)
Add support for CSS reading-flow (HTML PR #10613)
- More discussion is needed on the handling of tabindex before a resolution can be reached.
- The CSS spec does not yet have a FPWD due to some substantial questions against the draft, but the interaction with HTML was clarified.
Full Meeting Minutes
Minutes Telecon 2024-12-04
CSS Grid/Masonry (Issue #11243: Masonry Syntax Debate)
- The group discussed the proposals to decide if Masonry should be a part of Grid or a separate system
- Presentations were given by both sides explaining their views and reasoning
- They also discussed the TAG feedback which argued for a general approach of integrating display types further.
- At the end of the timebox the group did a strawpoll to see if there was a preference developing, however the results continued to be split. The two viewpoints will continue working on coming to a consensus approach.
Other Topics
- Resolved: Add Scroll Anchoring 1, CSSOM 1, and Color 5 to Rough Interop; add Nesting once it’s republished. (Issue #9793: Add specs to Rough Interoperability)
- Resolved: Add Selectors 4 to Rough Interop (Issue #9793)
- There was an openness to clarifying the definition for issue #10605 (Intrinsic size of `img` / `video` with aspect ratio but no definite size) however more thought was needed around describing the desired behavior so discussion will go back to github.
- Resolved: Allow consistent sideways-* and vertical-* writing modes to share a BFC (Issue #10714: Allow sideways-x and vertical-x to share a block formatting context?)
Full Meeting Minutes
Minutes Telecon 2024-11-27
- Split PR #11137 (Add automation support for viewport segments) into two. One PR with the editorial changes and one issue with the meta question about if we add web driver items in specs.
- Resolved: Adopt forthcoming UTR#59 as basis for text-autospace character classifications (deferring question of default behavior to a new issue) (Issue #11013: Use the Unicode East Asian Auto Spacing for `text-autospace`)
- Resolved: Adopt edits; open a new GH issue to discuss the name and highlight issue in spec (Issue #3473: Preventing too-short final lines of blocks (Last Line Minimum Length))
- Resolved: The pseudoElement argument to getComputedStyle takes any pseudo-element selector, and selects the first matching pseudo-element like querySelector() (Issue #4456: getComputedStyle for ::before::marker or ::after::marker)
- There was not consensus if issue #11014 (Clarification font-variant-emoji should not affect characters `0-9#*`) should be solved in CSS or in Unicode. Discussion will continue on the github issue.
- The winter F2F is Wed-Fri Jan 29-31 2025 at Apple Park
Full Meeting Minutes
Minutes OpenUI-WHATWG/HTML-CSSWG Joint Meeting 2024-11-21
OpenUI-WHATWG/HTML-CSSWG meeting
Selectors
- The group agreed to remove :closed for now and keep :open (Issue #11039: Should we have :open and :closed?)
CSS UI
- Resolved: Use currentColor for borders, inherit the color, transparent background color (for in-page controls). Use system colors for pickers (Issue #10909: Colors to use for appearance:base `select`)
- jahrar presented slides for issue #10857 (UA stylesheet for appearance:base `select`) and requested feedback and questions in github.
Full Meeting Minutes
Minutes Telecon 2024-11-20
- Resolved: Name the pseudo-element ::checkmark (Issue #10908: Pseudo-elements for checkmark and dropdown icon for appearance:base `select`)
- Resolved: Go with ::picker-icon (Issue #10908)
- noamr introduced the proposal to remove ‘auto’ (Issue #10995: Allow an auto-generated `view-transition-name` that doesn’t default to ID). There were objections to the removal so discussion will return to github.
- Resolved: Close no change (Issue #11097: Should forced-colors support `color-mix()`?)
- Resolved: Rename “overflowing” to “scrollable” (Issue #11182: scroll-state(overflowing) is confusing because it ignores clipped overflowing content)
Full Meeting Minutes
Minutes Overflow Breakout 2024-11-20
- Resolved: Go with option 2 and make them siblings (Issue #11125: Tree structure of scroll container controls)
- Resolved: Choose option 2 [Before Markers, Buttons, Content, After Markers] in the issue (Issue #10912: Focus order of generated controls)
- Resolved: Adopt proposal to anchor to identified elements (Issue #10738: Allowing markers to be active even when not scrollable to aligned position)
- Resolved: Use :target-current for the name (Issue #10918: Bikeshed pseudoclasses for active scroll-marker)
- Resolved: Accept flackr’s proposal in the issue (Issue #11216: Disabled scroll-button state and styling)
- Resolved: Go with Option 5 [Distribute some amount of the initial and ending scroll] (Issue #11165: Scrolling to unreachable scroll aligned marker positions)
- Resolved: Publish Overflow 5 as FPWD
Full Meeting Minutes
Minutes Telecon 2024-11-13
- Resolved: Publish new WD of View Transitions 2
- Resolved: Republish Pseudo 4, move glazman to former editor
- Resolved: Publish new WD of Nesting
- Resolved: Add new category, shorthanded as “reliable CR” (Issue #9770: Add specs to Official Definition)
- Resolved: Add Media Queries 4 and Scroll Snap to “reliable CR” (Issue #9770)
- Resolved: Move Grid 1 and Grid 2 to “reliable CR” (Issue #9770)
- Spec editors are asked to post their opinions of where those specs should be placed in the snapshot so that the group can do a bulk set of resolutions in the near future.
- Resolved: Accept proposal to use type(`syntax`), add string, and add units as keywords (Issue #11035: attr() and forwards compatible parsing)
- Resolved: Accept the changes to the shape() grammar (Issue #10649: `curve to` keyword `using` seems a bit off)
- Resolved: Using ‘border-area’ in the background shorthand (and omitting origin) defaults the origin to border-box (Issue #11167: Default background-origin for `border-area` in shorthand)
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: