Minutes Telecon 2021-10-13
- Resolved: CSSWG meeting scheduled for 8am Pacific next Wednesday, first item issue #6520
- Resolved: Define gamut-mapping using OKLCH and OKdeltaE (Issue #6642: Add OKLab, OKLCH)
- Resolved: For non-legacy color formats, use OKLAB for interpolation by default (instead of CIE LAB) (Issue #6642)
- Resolved: Add syntax to represent OKLAB and OKLCH colors (Issue #6642)
- Resolved: Add oklab() and oklch() (Issue #6642)
- Resolved: Add these as keywords to color-mix() (Issue #6642)
- Resolved: Add these to color adjustment functions also (Issue #6642)
- Resolved: No substantive change to spec, but clarify the text to avoid confusion (Issue #6693: Content size suggestion of large flex items)
- Resolved: Defer state queries to L2 (Issue #6402: Define a syntax for state-based container queries)
- Resolved: Add root-relative variants of *all* the font-relative units, named r* (Issue #6034: Adding new relative units RCH and REX)
Full Meeting Minutes
Minutes Telecon 2021-10-06
- Resolved: We will have 2 separate objects; one for rules without a block and one for rules with a block (Issue #6576: Cascade Layers need CSSOM support)
- Resolved: Reverse the prior resolution. Unlayered styles are highest priority (Issue #6284: Reconsider placement of unlayered styles, for better progressive enhancement?)
- While discussing issue #6284, the group agreed that the author control of priority was necessary in the first level of the spec since there are strong use cases for any order and therefore authors needed to be able to override the default.
- Resolved: Leave the spec unchanged with dot syntax (Issue #5791: What is the appropriate syntax for appending to nested layers?)
- Resolved: Presentation hints into their own origin between user and author in cascade (Issue #6659: Cascade priority of presentation hints vs. tree scopes)
- Resolved: Keep “layers” and close issue no change (Issue #5840: Layers terminology bikeshed)
- Resolved: Use cq as the prefix (Issue #5888: “container width” and “container height” units)
- There should be guidance created to determine when a unit should be created in order to avoid an explosion of units.
- Resolved: Accept proposal in ED. Split range syntax and attributes to new issue (Issue #6396: Define a syntax for style-based container queries)
- Resolved: Add a matchContainer method as proposed in issue. Keep issue open to decide if need new observer or if we can reuse the existing (Issue #6205: Similar to window.matchMedia, Container Queries should have a similar method)
- Resolved: Add the new attribute of highlight type which is an enum (Issue #6498: Figure out how highlights are exposed to the accessibility tree)
- Resolved: Add spelling-error, grammar-error, and highlight (Issue #6498)
- Further discussion about how the highlights are exposed in Issue #6498 should be added to the TPAC meeting agenda with the APA group.
- Resolved: Take scientific notation and match serialization of JS (Issue #6471: Serialization of large numbers should use scientific notation)
- The group didn’t think auto-darkening should be linked to forced colors mode since auto-darkening appears to happen at paint time. Discussion will continue on issue #6664 (Forced colors mode usage beyond high contrast mode).
- Resolved: min-height:auto just has special behavior that allows child %s to still resolve, and it’s not a precedent to apply to all the other content-based keywords. (Thus, we’ll remove, or possibly keep-but-reverse, the note that’s currently in the spec.) (Issue #6457: Definiteness of min-height: min-content)
- Resolved: The offsetWidth and offsetHeight should be computed out of the principal css box (Issue #6588: Needs more details for offsetWidth and offsetHeight)
- Resolved: It should include all fragments (Issue #6588)
- Discussion will continue on Issue #6588 on how to answer how to decide if a block is split does the block doing the splitting get included in the calculation
Full Meeting Minutes Part I and Part II
Added interpolation function to CSS Values and Units 4
The CSS Working Group has published an updated Working Draft of CSS Values and Units Level 4. This specification defines the CSS property definition grammar, and the value types that are common across many specs, such as <length> or <string>.
New to this draft is the interpolation function mix() which accepts a percentage representing linear progress between two values. More advanced interpolations are also being discussed for Level 5, see e.g. Issue 6245.
Other changes since the last Working Draft are all listed in the Changes section.
Please send feedback by either commenting 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-values-4]) and your comment topic in the subject line. (Alternatively, you can message one of the editors and ask them to forward your comment.)
Minutes Telecon 2021-09-22
- Resolved: margin-trim applies to flex and grid containers also (Issue #3255: Should margin-trim apply to flex or grid containers?)
- There was difference in the behavior expected by authors and the implementation behavior for issue #3256 (Should margin-trim have a ‘floats’ value?). Conversation will continue on github to gather the use cases in order to determine the best solution.
- Resolved: margin-trim determines which sides to apply to as described in #6643 (Issue #6643: Switch margin-trim to boolean indicating sides rather than types of boxes to trim)
- There are several test cases outlined in issue #6609 (Directionality inheritance into Shadow DOM) that need to be reviewed to see if the behavior the tests describe is correct. fantasai offered to review, but anyone interested should also look at the github issue and provide feedback.
- The proposal for issue #5469 (Should forced-colors override border-image?) is to continue leaving border-image as-is and add language to explain the rationale and that it’s limited to border-image.
Full Meeting Minutes
Minutes Telecon 2021-09-15
- Resolved: Adopt if/else as next level of css-conditional (Issue #6520: Nesting @supports inside @font-face / font tech queries)
- Resolved: Accept the PR (Issue #6520)
- There are still some open questions and concerns around issue #6520 that were discussed on the call, but they will be raised as separate issues.
- Resolved: Transition css-multicol-1 back to CR (Issue #6612: New CR?)
- Resolved: Add a note [this falls out from the computed value definition] (Issue #6586: What is the serialization “background-position: top right 10px”?)
- Resolved: Serialize as url(“”) (Issue #6447: Serialization of empty url() undefined)
Full Meeting Minutes
Minutes Telecon 2021-09-08
- There are calls scheduled with i18n and a11y on 20th and 27th. Please tag Agenda+TPAC on issues that should be discussed during those calls.
- Please review the updated spec text for Positioned Layout 3. Next week there will be a request for republication.
- Resolved: Close no change: taking BR out of flow removes its effect on the surrounding content, just like every other element (Issue #5749: What is the behavior of an absolutely-positioned
br?)
- Resolved: Reference DOM’s definition of invalidity for static ranges for highlight API (Issue #5497: Invalidation of Static Ranges)
- Resolved: Republish Highlight API
- Resolved: Retitle CSS Scrollbars to CSS Scrollbar Styling (Issue #6549: Improve title)
- Resolved: Republish CSS Scrollbar Styling
- Resolved: Move css-color-adjust-1 to CR
- If a decision isn’t reached on issue #5469 (Should forced-colors override `border-image`?) before the CR publication it will be noted inline as an open issue.
- Resolved: Add marquee to compressible elements (Issue #6342: Add
marquee to list of compressible elements)
- chrishtr will take the lead on reviewing the differences between Gecko and Blink implementations of hit testing. There is still no volunteer to try and specify hit testing, but the group would be interested in doing so if anyone does step forward.
Full Meeting Minutes
CSS Display Level 3 updated to include ‘order’ and ‘visibility’
The CSS WG has published an updated Candidate Recommendation of the CSS
Display Module Level 3. This module describes how the CSS formatting box tree is generated from the
document element tree and some properties to control the type, order, and visibility of those boxes. This update:
All significant changes since the last CR are listed at in the Changes section, and a disposition of comments since the last CR is available.
Please review the draft and send 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-display-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
It is our intention to post an updated CR Snapshot of this module as soon as horizontal review is completed.
Minutes Telecon 2021-09-01
- Resolved: Add fantasai and chris as editors for Conditional L4
- More volunteers are needed to create short videos for TPAC. The deadline to volunteer is 15 September.
- Resolved: scroll-snap-align and future 2-axis properties use the logical model (Issue #2988: ‘overflow’ 2-value syntax is in wrong order)
- Issue #2971 (Confirm interaction of positioned elements and continue:discard) needs more feedback from implementers familiar with the fragmentation model in order to reach a decision.
- Resolved: Expand the color stop hint grammar with easing functions and define how gradients respond to that (Issue #1332: Add easing functions to color stops)
- Another issue will be opened to explore if we should continue to have smart interpolation of gradients given they have no implementations and add complexity to the above resolution.
- Resolved: Move the work miriam has done to cascade L6 (Issue #5809: Proposal for light-dom scoping/namespacing with re-designed @scope rule)
- Resolved: Take the css-shadow-parts and css-scoping drafts, integrate them, and republish as css-shadow
- Resolved: We are going to start specifying a no motion at all mode that makes motion inducing animations discrete between keyframes where keyframes are sufficiently separated in time (Issue #5321: TAG feedback: interaction with prefers reduced motion)
- Once the no motion mode property is more fleshed out the group will return to the discussion about how to create Media Queries around the new property.
Full Meeting Minutes
CSS Cascading and Inheritance Level 5 Draft Updated
The CSS Working Group has published an updated Working Draft of
CSS Cascading and Inheritance Level 5.
This CSS module describes how to collate style rules and assign values by way of cascading and inheritance.
Level 5 adds “layers” to the cascade, along with a syntax for defining and sorting those layers. In the same way that cascade origins provide a balance of power between user and author styles, cascade layers provide a structured way to organize and balance concerns within a single origin – such as element defaults, third-party libraries, themes, components, and overrides.
The changes have been made since the previous Working Draft:
- Reserve the CSS-wide keywords for future use in layer-names.
- Clarify that @layer rules respect global conditional rules, but are always applied to the layer order when declared in non-global conditions such as a container query.
- Clarify that name-defining at-rules follow layer order for collision resolution, similar to specificity resolution.
- Disallow interleaving of @layer with @import or @namespace rules.
Please send 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-cascade-5]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Scrollbar Styling Last Call Working Draft
The CSS Working Group has published an updated Working Draft of CSS Scrollbar. This CSS module defines properties to influence the visual styling of scrollbars, introducing controls for their color and width.
Having addressed all outstanding comments, we expect to take transition to Candidate Recommendation after completing horizontal review. So please consider this the last call for comments prior to CR! Changes since the last Working Draft are listed in the Changes section.
Please send 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-scrollbars-1]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: