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:
- Unlayered styles now have the lowest priority in normal origins, rather than the highest. This is designed to help with author expectations and progressive enhancement, so that more explicit layers have a higher weight than the default, while unlayered
!important styles remain at the top of the priority order.
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.)
Minutes Telecon 2021-06-09
- Resolved: Accept the edited changes as described by florian (Issue #4674: scrollbar-gutter is too complex) [Edits | New Appendix]
- Resolved: Accept changes and add only keyword (Issue #5089: Re-add only to mean “don’t auto-adjust me”, per WebKit’s behavior)
- Resolved: Add forced-color-adjust propagation to apply to root (Issue #6307: viewport propagation of forced-color-adjust)
- Resolved: Add color-only value as described in the issue and clarified by TabAtkins (Issue #6310: Spec currently breaks use of currentColor for SVG icons in WHCM)
- Resolved: Accept the proposal [Add an exception to the general comma-omission rules] (Issue #6345: Whitespace-trimming and custom properties)
- Resolved: Add contain:paint to list of grouping properties (Issue #6202: Should it be possible for an element with contain:paint to be part of a transform-style:preserve-3d scene?)
- Resolved: Adopt this media feature as a part of Media Queries (Issue #6343: Display mode media feature)
- A grid of possible cases will be added to issue #6341 (Compressible elements with aspect ratio) in order to clarify the expected behavior.
Full Meeting Minutes
Minutes Telecon 2021-06-02
- Resolved: Make all predefined symbolic counter styles not overwritable (Issue #3584: overriding symbolic counter styles)
- Resolved: When you extend a predefined symbolic you are extending the version defined in the spec (Issue #3584)
- Resolved: Leave the spec as it is and have browsers fix the bug (Issue #5906: Change how ‘pad’ descriptor handles negative sign to match implementations)
- Resolved: Accept the PR linked in the issue defining how counter style scoping works with shadow dom (Issue #5693: Clarify how @counter-style name lookup works with shadow DOM)
- Resolved: Add ‘custom’ value to prefers-contrast for defined color schemes that are not more or less (Issue #6036: Remove (prefers-contrast) as a boolean, and replaced by a new color reduction media query)
- Resolved: We consider informal spellings to be typos to be fixed when found and avoided if possible (Issue #5850)
Full Meeting Minutes
Minutes Telecon 2021-05-26
- Resolved: Republish WD of Color 4 & Color 5
- Resolved: Only apply contain-intrinsic-size: auto with content-visibility: auto (Issue #6308: Only apply contain-intrinsic-size: auto with content-visibility: auto)
- The use case described in issue #6257 (Removing intrinsic aspect-ratio from an image) is better achieved by contain:size. The group is open to adding aspect-ratio:none but needs more use cases to determine if it’s necessary.
- Resolved: Accept the new reorder layering as detailed in the issue (Issue #6284: Reconsider placement of unlayered styles, for better progressive enhancement?)
- In addition to the default agreed upon above there is interest in further exploration into allowing authors to define which layer should be exposed to older browsers.
- Resolved: Tentative agreement on the spec text as in the draft. Subject to further review of current interop behavior (Issue #1995: Handling global name-defining constructs in shadow trees)
- TabAtkins will put together the change log and then request a republication of Scoping.
- Resolved: Container queries are triggered by independent property (name to be bikeshed) (Issue #6174: Should there be a new syntax for establishing queryable containers?)
Full Meeting Minutes
The CSS Working Group has published an updated Working Draft of CSS Box Sizing Module Level 4. This module defines the sizing properties (width/height/etc.) and their keywords. It is currently drafted as a delta spec over Level 3 and introduces new features such as aspect-ratio and contain-intrinsic-size (see list of additions to Level 3).
This module is still under heavy revision; 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-sizing-4]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Color Adjust Level 1 updated WD
The CSS Working Group has published an updated Working Draft of CSS Color Adjustment Level 1. This module introduces a model for and controls over automatic color adjustment by the user agent to handle user preferences, such as “Dark Mode”, contrast adjustment, or forced-contrast color schemes.
At this point we have only two open issues: Controlling auto-darkening and Shielding system colors to avoid fingerprinting? (see current CSSWG position; we’re awaiting review by the TAG/Accessibility/Privacy horizontal review groups). We expect to transition to CR once these are resolved.
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-color-adjust-1]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minutes Telecon 2021-05-19
- Issue #1039 (CSSColorValue section needs WG review) brought to light many different concerns which need to be split into separate github issues and discussed. The biggest topic raised which will need further discussion is the scope of CSSColorValue and if it should be a generic color manipulation object. Since there are several items in front of TAG which relate to this question, it will need some prioritization for discussion once the issue is created.
- There was no strong opinion of which behavior to use on issue #6286 (Behaviour of SVG degenerate aspect-ratios) so the group will wait to hear back from AmeliaBR before deciding.
- There is enough need currently to include the only value in the first level of CSS Color Adjust (Issue #5089 (Re-add only to mean “don’t auto-adjust me”, per WebKit’s behavior)). smfr provided a link that describes the current WebKit behavior in order to guide the creation of spec text.
- Resolved: Add print-color-adjust as an alias for color-adjust and have the generic color-adjust be deprecated (Issue #3880: Combine forced-color-adjust and color-adjust properties somehow?)
- Resolved: Specify this in CSS Contain (Issue #5913: :root/body viewport propagation and containment)
- Resolved: If the used value of contain is other than the default we break propagation (Issue #5913)
Full Meeting Minutes
Minutes Telecon 2021-05-12
- Resolved: Confirm that abspos elemetns do not create column boxes and this adjacent spanners separated by abspos will collapse margins (Issue #6265: Definition of adjacent spanners, when to create column boxes)
- Resolved: Add the current interop situation to the spec [Out of flow positioned elements affect the height of the multicol container] (Issue #6279: Should contained out-of-flow descendants affect column balancing?)
- Resolved: Remove at-risk label for style containment (Issue #6272: Remove “at-risk” for style containment)
- Resolved: Style containment will be required in order to establish a queryable container (Issue #6213: Need style containment for container queries)
- Resolved: Have unknown @supports expressions evaluate to false for all @support rules (Issue #6175: What is the migration path for Container Queries?)
- Resolved: Create a container function that can test if @supports checks for a particular container query (Issue #6175)
- Resolved: Drop lab from color() (Issue #5887: Consider removing lab(…) and lch(…) syntax and using color(lab …) and color(lch …) only)
- Resolved: Make -webkit-image-set a parse time alias to image-set (Issue #6285: Consider making -webkit-image-set a parse-time alias to image-set)
Full Meeting Minutes
Minutes Telecon 2021-05-05
- Resolved: Specify option 1; match FF current behavior [the baseline is calculated the same as for visible] (Issue #6212: Baseline of an inline-block with overflow:clip)
- There was a strong leaning on the call to address having issue #4708 (Increase pointer target size independently of element layout) solved by browser behavior rather than having an explicit property which can be set. Some more research needs to be done on cases where current hit testing has issues, such as buttons with rounded corners, before a decision can be reached.
- Resolved: Have container MQ not resolve when there is no ancestor container (Issue #6178: How does @container resolve when no ancestor containers have been defined?)
- Resolved: If there is containment on body or root it stops propagation from body to root (Issue #5913: :root/body viewport propagation and containment)
- Within issue #6213 (Need style containment for container queries) is a motivating use case to do style containment which was previously missing. Given this new use case to handle counters and quotations the issue of style containment will be brought back up with those who previously objected to see if there’s now interest in addressing style containment.
- Resolved: Start with ex, cap, ic, and ch (Issue #6160: Extend font-size-adjust to take a pair of values:
metric number)
- A new issue will be opened to consider adding ascent and possibly descent to the above list.
Full Meeting Minutes
Minutes Telecon 2021-04-28
- Please start gathering thoughts and content for the 2021 snapshot on github in issue #6243.
- Resolved: No change to name; stay with size-adjust (Issue #6114: bikeshedding name of size-adjust descriptor)
- Resolved: Add from-font keyword to font-size-adjust [to Fonts 5] (Issue #5539: font-size-adjust: auto)
- fantasai will add details to issue #4818 (oblique angle for vertical text with text-combine-upright) about the difference in visual presentation this would introduce between regular italics and this property. Discussion will continue on GitHub
- The group will wait for more evidence of author demand before taking up issue #6104 (Consider ‘extends’ descriptor to reduce duplicate declarations)
- Resolved: Fonts with negative line gaps are clamp at 0 (Issue #5064: The web de-facto requires nonnegative line gap metrics in fonts)
- Resolved: Undo previous resolution. Treat replaced elements with an internal ruby display value as if they were inline at used value time (Issue #6000: Replaced annotation containers and base containers are nonsensical)
- Resolved: Close no change (Issue #6237: Add a :media pseudo-class, to match the set of elements matching the media pseudo-classes)
- Issue #6250 was filed to better define if Seek returns as playing or paused.
- Resolved: image-set should act like srcset attribute with applying resolution (Issue #6241: image-set() resolution should be applied on-top of, not instead-of the natural image resolution)
- Resolved: Switch to using 25AA (Issue #6200: counter-style square symbol (0x25FE) is bad)
- Issue #6175 (What is the migration path for Container Queries?) is reaching a conclusion to allow a user to test a container query property value pair. The final details will be worked out on GitHub.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: