Minutes Telecon 2025-09-17
- Resolved: Drop the fullscreen-* vars (Issue #11899: Add environment variables defined in WebKit)
- Resolved: Publish FPWD css-env-1
- Resolved: Add !important to UA stylesheet rule for the inert attribute (Issue #12049: The interactivity property should not be included in the all shorthand)
- Resolved: Add element.pseudoAll that returns a list of CSSPseudoElement (Issue #12162: Add a property to retrieve plural instances of pseudo elements with the same selector)
- Resolved: Go with ::clear-icon and ::reveal-icon (Issue #11845: Password visibility toggle)
- Several folks gave an overview of issue #12132 (Using logical keywords in background-position shorthand with multiple backgrounds) and, in discussing details, realized that creating a through write up would help further discussions and focus around the various considerations necessary.
- Resolved: Add a flexbox level 2 with flex balance feature, syntax TBD (Issue #3070: Add flex-wrap: balance;)
Full Meeting Minutes
Masonry Spec Update and Open Issues
The CSS Working Group has published an updated Working Draft of CSS Grid Layout Level 3, which defines masonry layout. Updates in this revision include defining “dense packing” for masonry, and clarifying baseline alignment and automatic track repetition. As published earlier, masonry layout re-uses the grid-* templating properties and the spec has sketched out an item-flow proposal to control orientation and placement order. See the WebKit Blog’s Item Flow, Part 1: A new unified concept for layout post for an overview of this idea.
There remain some major syntax questions open, which the Working Group is interested in broader feedback on:
- Enabling masonry layout: what
display name to use? This is a bit of a bikeshedding question, but we do want it to feel like masonry (essentially 1-axis grid layout) is a variation on grid layout (2-axis grid layout), so the CSS Working Group is looking for ideas that incorporate the keyword grid somehow.
- Interpreting row vs column in masonry layouts This starts to get into questions of what’s obvious at first glance vs what’s obvious when you integrate it with the rest of CSS, and the answers thus far are… murky. It would be good to get more authoring perspective here.
If you anticipate using masonry layouts, we’d appreciate your perspective on what would create the most intuitive (and error-resistant) system for you to learn and use, so let us know your thoughts!
As always, you can send feedback by either commenting on or filing an issue in GitHub (preferable) or sending mail to the (archived) public mailing list www-style@w3.org with the spec code ([css-grid-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes CSS Overflow Breakout 2025-09-17
- Resolved: Clarify the interaction between nowrap and block ellipsis (Issue #12811: nowrap and block-ellipsis)
- Resolved: Rendering should be equivalent to line breaking at that soft wrap opportunity, and applying white space processing part 2 before inserting ellipsis at the end (Issue #12008: Interaction between whitespace collapsing and line-clamp)
- Resolved: The region break set by line-clamp ignores widows/orphans (Issue #9235: How does `widows` and similar properties affecting fragmentation interact with `continue: discard`?)
- Resolved: Close no change until/unless users complain (Issue #12663: How do empty blocks affect line-clamping by height?)
- Resolved: Floats do not increase the height of a line clamp container. They are clipped to its content edge. (Issue #12665: Floats and line-clamp)
Full Meeting Minutes
Minutes Telecon 2025-09-10
- The group discussed the possible ways to address the fingerprinting issue raised in issue #10372 (Mitigating fingerprinting for AccentColor/AccentColorText) A focus of the conversation was if tainting the color so it paints correctly but doesn’t return an exact value could address this issue. The potential path forward would be tainting by propagating a computed color plus an additional bit. Concerns were expressed that if the group couldn’t figure out how to get AccentColor/AccentColorText to paint correctly then the feature itself would not have value.
- Resolved: Change ‘direction’ to ‘scrolled’, discuss keywords later (Issue #12623: Disambiguate scrollable/direction when along axis/towards edge)
- There wasn’t disagreement with the proposal raised in issue #12652 (animation-trigger CSS syntax) to have the event or action be optional in the new trigger() property. However, there was still a lot of discussion on the broader syntax and bikeshedding so a resolution on this specific question felt premature.
Full Meeting Minutes
Minutes Telecon 2025-09-03
- Resolved: Change the definition to ‘must do nothing’ and make the computed value remain (Issue #12015: What to do with `blink` value in `text-decoration`?)
- Resolved: Change initial value of item-tolerance to ‘normal’ (Issue #12111: Make `item-tolerance` initial value `normal`)
- The group discussed the options in github for issue #12176 (Giving ::scroll-marker-group a name (and optionally text))
- There was disagreement about if this type of labeling is the scope of CSS or the scope of HTML. :before and :after allow the labeling so there is a precedent, however a11y guidance is away from that use case so it’s unclear if it’s a path that should be followed.
- General questions about scroll markers being in CSS were also discussed with this as another example of how this property blurs the lines between CSS and HTML.
- Discussion will return to github with examples added to hopefully make the issue less abstract.
- Resolved: line-clamp: integer with a height constraint clamps by height or by lines, depending on what comes earlier, pending compat issues (Issue #12041: Can you line-clamp by both a number of lines and a height at the same time?)
Full Meeting Minutes
Minutes CSS Snapshot 2025 Breakout 2025-09-03
Full Meeting Minutes
Minutes Telecon 2025-08-13
- Resolved: Use :interest-source and :interest-target (Issue #12515: Suggest a better name for the `:interest-target` pseudo class)
- There were concerns about the proposal for issue #12040 (`getClientRects()` should return a flattened list of child rects for `display: contents`) limiting anchor positioning or parts users so discussion will return to github.
- Resolved: Define that subgrid repeat works exactly the same as grid repeat (Issue #8493: Subgrid auto repeat calculation when `line-name-list` size isn’t a multiple of remaining subgrid tracks)
- Resolved: Create level 2 diff spec for anchor pos and define an anchored keyword for container-type there (Issue #12390: Add a new container-type `anchored` for querying anchored elements)
- Resolved: Define a fallback container feature used in the anchored query function (Issue #12391: Add a `fallback` feature for querying applied fallback for anchored elements)
- Resolved: Add three methods to AnimationTrigger interface: addAnimation, removeAnimation and getAnimations (Issue #12397: How do AnimationTriggers attach to animations?)
Full Meeting Minutes
Minutes Telecon 2025-08-06
- Resolved: Republish Color Adjust
- Resolved: Pursue this functionality in HTML. Close this issue. (Issue #12437: Add a `::interest-hint` pseudo element to interest invokers)
- Resolved: All percentages (insets, sizes) resolve against the effective containing block (no inconsistency) (Issue #10861: Introduce “document containing block” for some purposes?)
- The solution for issue #12371 (Define precisely when anchor recalc points happen, and which offsets it captures) is potentially editorial and needs to be investigated a bit further. Directionally, the proposal is anchor positioned boxes recalculate layout for all changes that might affect their size/position except scrolling except for special recalculation points.
- Resolved: Make Animation Trigger related things readonly (Issue #11918: Should AnimationTrigger properties be readonly?)
- Resolved: Adopt syntax ‘columns: [
column-width || column-count ] [ / column-height ]? (Issue #12050: `columns` shorthand with `column-height` and `column-wrap`)
- Resolved: Shorthand ‘columns’ also resets column-wrap (if it exists) (Issue #12050)
- Resolved: Don’t use env() for this. Use an @page descriptor roughly as proposed by dholbert; work out details in the issue. (Issue #11395: Expose unprintable areas via CSS)
- Resolved: Accept Elika’s bullet points in the last comment (Issue #8842: Float and first-letter pseudo-element interaction missing from the latest specs)
Full Meeting Minutes
Minutes Gap Decoration Breakout 2025-08-06
- Resolved: Change name to rule-overlap (Issue #12540: Bikeshedding rule-paint-order)
- Resolved: Update definition of gap with gutter terminology (Issue #12084: Gap intersection point definition might need updating for multi-col)
- Resolved: Apply all decorations from left to right (Issue #12527: Values after an auto repeater when there’s fewer values than gaps)
- Resolved: Define gap decoration animations using LCM methods (Issue #12431: Define interpolation behavior)
- astearns will tag additional folks in issue #12201 (Serializing `column-rule` shorthand from separate longhands) to get those with expertise in shorthands to weigh in.
Full Meeting Minutes
Minutes Telecon 2025-07-30
- Resolved: Add CSS URL to “Safe to Release pre-CR Exceptions” of 2025 Snapshot. (Issue #12539: Add CSS URL modifiers to the 2025 snapshot)
- Before deciding on issue #12482 (Add CSS `random()` function to the 2025 Snapshot) the group will get wide review on random().
- Resolved: If multiple values are omittable in serialization, but at least one is required, choose the first one in grammar order unless constrained by compat. (Issue #12486: Clarify expected computed value for `text-decoration` and similar shorthands (can we omit resolved `currentColor`?))
- Resolved: If a `color` value is omittable when computed to currentColor, then it is omittable even though the resolved value is not the ‘currentColor’ keyword (because colors are absolutized), unless constrained by compat. (Issue #12486)
- Resolved: When only one auto inset, ‘normal’ alignment with position-area resolves to the alignment that attaches to the non-auto edge. (Issue #12512: More intuitive alignment defaults when using one-sided insets)
- There was broad agreement that the current behavior mentioned in issue #10258 (Handling popover default styles) was confusing and needed to be fixed. There are concerns that the proposal may not be compatible and may make styling difficult. Discussion will return to github to investigate further.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: