CSS WG Blog front page (original) (raw)
Minutes Telecon 2025-04-30
- Resolved: Publish FPWD of CSS Custom Functions
- Resolved: Copy linear gradients timing details into the linear function (Issue #11211: Resolving curves not available at parse time)
- Resolved: Remove the event (Issue #7693: No event to track window position)
- Resolved: Add scrollParent to the spec (Issue #1522: Consider adding Element.scrollParent)
- Resolved: All CSS-defined functions serialize to lowercase (unless otherwise defined), just like CSS-defined identifiers (Issue #11556: Serializing of functions)
Minutes Telecon 2025-04-23
- Resolved: Have sibling-index() and sibling-count() to default to DOM tree (Issue #9562: Allow specifying flat vs light tree in `sibling-index()` and `sibling-count()`)
- Resolved: Adopt spec text as quoted, i.e. no change to spec. (Issue #11195: Absolute positioning – Is the new inset & auto-size behaviour web-compatible?)
- The proposal for issue #11926 (Nested ::view-transition-group should have a container pseudo) was to add new new container. Through discussion there were initially questions about expected behavior and if the complexity was worthwhile. More examples will be added to the issue including the broader context of what use cases this would impact.
Minutes Telecon 2025-04-16
- Though issue #10674 (UAs inconsistent in how OS font settings affect the default font-size `medium`) was brought for a resolution on the name, through conversation the group discovered a lack of clarity around what are the different behaviors across browsers and devices. In addition to names, it was suggested something like an explainer be created that lays out the various behavior combinations and expected results to help guide understanding.
- Resolved: Working title is preferred-text-something (Issue #10674)
- Resolved: Working title is preferred-text-scale, continue work on defining how it interacts with all the zooms and things (Issue #10674)
Minutes Color HDR Breakout 2025-04-09
Color HDR Breakout
- Require `H2 >= H1`? (Issue #11787)
- Resolved: Require strict inequality for H1 and H2
- 2.4 “two dynamic-range-limit-mix values” should be “two or more …” (Issue #11694)
- Resolved: Allow single value, well defined
- Auto value of dynamic-range-limit (Issue #11558)
- There was general agreement to add an auto value, but not yet agreement on how it should behave. Folks will keep thinking about the behavior and come back to this issue.
CSS Grid: Level 1 & 2 updated, Level 3 (masonry layout) reworked
The CSS Working Group has published an updated drafts of all three levels of CSS Grid: CSS Grid Layout Level 1, CSS Grid Layout Level 2, and CSS Grid Layout Level 3. The update to Levels 1 & 2 are largely adjustments to the core layout algorithm (see changes); the update to Level 3 (which was published in early February) resolves a few key debates in masonry layout and opens up some additional design questions (see overview).
The early drafts of CSS Grid Level 3 contained two competing proposals. The February update incorporates the CSS Working Group’s resolution to re-use the grid-* properties for track templating and item placement, and, prompted by feedback from W3C’s Technical Architecture Group (TAG), sketches out a new direction for controlling layout flow using a unified set of properties that would work across both Flex and Grid layout. There are still many unsettled debates for in this model, but also excitement about the possibilities that have been opened up.
The CSS Working Group invites feedback by either 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]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Color HDR Breakout 2025-03-26
Color HDR Breakout
- Initial value of `dynamic-range-limit` (Issue #11429)
- If the default is constrained originally it can be fixed later, but no-limit would need to stay in place. However, there are concerns about SDR being too strong a presence and holding back HDR growth.
- There is more research needed to reach a decision. smfr will check if the default for video could be constrained and ccameron will check what’s possible to share about limiting HDR on ad networks.
- Add target HDR headroom to `CanvasRenderingContext2D` (WHATWG Issue #11165)
- The group reviewed the proposal, available here.
Minutes Telecon 2025-03-26
- Resolved: When aspect-ratio is non-initial, then min-size:auto serializes as ‘auto’ in gCS() (rather than being censored to 0) (Issue #11716: Resolved value of min size properties doesn’t round-trip)
- Resolved: Accept the proposal for changing random caching as stated in the issue (Issue #11742: Maybe min, max and step should not be part of the random-caching-key)
- Resolved: Go with element-shared for now, keep renaming issue open because many people are unhappy with it (Issue #11742)
- Resolved: Initial value of reading-flow is “normal” (Issue #11396: Initial value of `reading-flow`)
- Resolved: Add ‘source-order’ value applying also to block containers (Issue #11396)
- Resolved: No change to the default behavior for reading-flow and dense grid for now, because there’s no proposal (Issue #11396)
- The question as to if reading-order should work by default that is included in issue #11396 will remain open while Apple consults their accessibility team.
Minutes Telecon 2025-03-19
- Resolved: Publish FPWD of CSS Forms
- Resolved: Editors will figure out how to fix the OM to match the new behavior, and bring it back to the group for review (Issue #10845: `CSSContainerRule.containerName`/`containerQuery` should return a list)
- Resolved: Drop `:host-context()` (Issue #1914: Dynamic changes of state and attributes referenced by :host-context rules are pretty hard to handle efficiently)
- Resolved: Accept the epsilon proposal, with follow-up refinements as needed (Issue #11864: Make UA, not author, deal with floating point errors in random())
- The folks on the call were leaning toward accepting the proposal for issue #11742 (Maybe min, max and step should not be part of the random-caching-key), however they wanted more time to discuss the concerns in the issue.
Minutes Color HDR Breakout 2025-03-12
Color HDR Breakout Session
- There was not clarity on the goal of issue #11558 (auto value of dynamic-range-limit) so discussion will return to the mailing list.
- The debate on issue #11429 (Initial value of `dynamic-range-limit`) focused on what was the best behavior for the web.
- One position was to not limit by default and make sure it’s clear when an HDR image is too bright as it will encourage authors to make good content. The concern with that approach is that authors may have a hard time figuring out how to fix their content.
- The other position was to have an opt-in so that the content was presented well by default but authors with expertise will be able to leverage the properties. The concern with that approach is that it may not be the best once HDR is the prevalent content.
- Folks then discussed their goals for the property to leverage those goals and reach consensus.
- There was a slight lean to have a sdr default with video override, however a key voice wasn’t on the call so discussion will return to github.
Minutes Telecon 2025-03-12
- Resolved: view-transition-name:auto never matches an explicit view-transition-name:`ident` (Issue #11614: view-transition-name: auto when matching id should namespace)
- Resolved: Change the way medium-safety alignment is handled to instead invoke the scroll adjustment machinery when handling an anchorpos fixpos element (Issue #10860: Default safety and fixpos)
- Resolved: Autospacing happens *after* bidi-reordering, and we’ll add a complex example to the spec (Issue #10803: Spacing across element boundaries for BiDi content)
- Resolved: No normative change to spec, but add example like Oriol’s and make the implication clearer in the spec. (Issue #10721: Content contribution of min-inline-size:fit-content and max-inline-size:fit-content)
- Resolved: For the final step in determining natural sizes, use the determined aspect-ratio to coerce the block size to match (Issue #11236: How to transfer intrinsic keywords via aspect ratio?)
- Resolved: Add a ‘size’ shorthand property (for ‘width’/’height’), no relation to @page’s ‘size’ descriptor (Issue #820: Adding a ‘size’ shorthand for ‘width’/’height’)
- When discussing issue #11716 (Resolved value of min size properties doesn’t round-trip) the group discovered that the proposed behavior may already be done in flex and grid. There wasn’t time to discuss further on the call, but folks will investigate further to resolve next week.