CSS Box Sizing Level 4 First Public Working Draft
The CSS Working Group has published a First Public Working Draft of CSS Box Sizing Module Level 4. This module defines the sizing properties (width/height/etc.) and their keywords, a long with related sizing terminology and concepts.
The module is currently drafted as a delta spec over CSS Sizing Level 3. (We will merge in the L3 prose once it reaches CR.) Additions since Level 3 include:
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.)
Minutes Telecon 2020-05-20
- Resolved: The color computed values are defined as used values using the color-mix function (Issue #4915: Is forced background-color computed or used value?)
- Resolved: Expose this selector and name it ::file-chooser-button (Issue #5049: Can you standardize a pseudo-element selector for file inputs?)
- The concerns about the spec allowing a ‘revert’ at computed value time (Issue #4155: Revert at computed-value time) may be addressed by the proposed !override property so as that’s written this issue will be re-reviewed.
- Resolved: Percent based gaps for flex in the cause of undefined constraint resolve to 0 (Issue #5081: Make flex % row-gap resolve to 0 when height is indefinite (only flex, not grid))
- Most of the group was okay with deprecating speech (Issue #1751: Deprecate ‘speech’ media type as well?) but needed to hear from others before resolving.
- There wasn’t enough time on the call to dive deeply into issue #5044 (length units in video-* media features) but there was interest to continue conversation about the expected behavior for the video-* properties on github.
Full Meeting Minutes
CSS Positioning Level 3 Rewritten
The CSS Working Group has published an updated Working Draft of CSS Positioning Level 3. This module contains defines coordinate-based positioning and offsetting schemes of CSS: relative positioning, sticky positioning, absolute positioning, and fixed positioning.
This update completely rewrites the entire spec for editorial clarity, technical precision, and compatibility with CSS Box Alignment, CSS Writing Modes, and CSS Display. There should be no differences in behavior from CSS2.1, so please report any inconsistencies as errors. (We’ve temporarily preserved some of the old absolute-positioning text for comparison.)
We’ve also posted a minor update of CSS Display Level 3 to better integrate the cross-references across the two specs and ensure that all of the relevant CSS2.1 prose (particularly around the definition of containing block) as been uplifted to Level 3.
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-position-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 Telecon 2020-05-13
- Resolved: Publish updated WD of position-3
- Resolved: Publish new CR of display-3
- Resolved: Publish a FPWD of sizing-4
- Resolved: Close issue #333 (Aspect Ratio) as fixed [it is a part of sizing-4]
- The migration path for custom origins (Issue #4985) can’t be finalized until there’s a more complete proposal.
- It’s important to have a migration path so that authors can use this before every browser supports it.
- Having a way to query support will be important for authors.
- Polyfills may be the path forward, but it depends on where the custom origins fall in specificity.
- Resolved: Call these “cascade layers” (Issue #4981: Better name for “custom origins”?)
- The final design for issue #4971 (How do custom origins interact with `!important`?) will need to wait until the definition is more fleshed out.
- There was interest in using this as a chance to re-think how to handle the use cases currently addressed by !important to see if there’s a different way it can be done which is more inline with the cascade layers approach.
- Resolved: Close no change, this is an intended difference (Issue #4126: Input stream processing can calculate wrong encoding)
- Resolved: Rename collapse value [of ruby-merge] to merge (Issue #5005: Rename ruby-merge: collapse to ruby-merge: merge)
Full Meeting Minutes
Updated WD of CSS Text Decoration Level 4
The CSS Working Group has published an updated Working Draft of CSS Text Decoration Level 4. This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks. Level 4 adds additional controls over these decorations, particularly their positions and skipping behaviors.
This update folds in the entire contents of the Level 3 specification (so that it is no longer a delta spec), splits text-decoration-skip into longhands, and makes some additional adjustments to the new features. Changes since the last Working Draft are listed in the Changes section.
A few of these new features (e.g. text-underline-offset and text-decoration-thickness) have already been implemented; others are in rough draft states (most of these are marked as such) and still need some design work. The next draft will hopefully solidify these rough features and shift remaining work more towards refining details.
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-text-decor-4]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)h
CSS Ruby Layout Level 1 Updated
The CSS Working Group has published an updated Working Draft of CSS Ruby Layout Level 1. “Ruby”, a form of interlinear annotation, are short runs of text alongside the base text. They are typically used in East Asian documents to indicate pronunciation or to provide a short annotation. This module describes the rendering model and formatting controls related to displaying ruby annotations in CSS.
This update folds in a number of changes and corrections for issues reported since the previous draft in 2014 (primarily by Mozilla’s implementation team and the Internationalization Working Group, thank you very much!). It also adds some basic control over ruby overhang behavior. Changes since the last Working Draft are listed in the Changes section.
There are still a number of known issues open, so we expect some heavy revision over the next year. Issues are currently tracked in two places: a disposition of www-style comments and in CSSWG’s GitHub repo.
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-ruby]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Box Model Level 3 Split: FPWD Level 4
The CSS Working Group has published an updated Working Draft of CSS Box Model Module Level 3 and a First Public Working Draft of CSS Box Model Module Level 4. This module describes the margin and padding properties, which create spacing in and around a CSS box.
The new Level 4 draft is a copy of the previous Level 3 draft; all new features since CSS Level 2 have been dropped from the Level 3 draft so that it can be used as a reference base for the various layout specs now in CR.
- CSS Box Model Level 3
- CSS2 + rebased descriptions on top of CSS Writing Modes + more definitions of terms to improve referencing across CSS specs
- CSS Box Model Level 4
- Level 3 +
margin-trim proposal
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-box]) 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 2020-04-22
- The virtual F2F will be two days, April 29 and 30. There are two possible time slots so working group members are asked to mark on the wiki what time zones work for them and what topics they would like to attend. This will allow the chairs to decide which timeslots to use and how to schedule the agenda topics. The F2F will be held over Meet with links sent out to the private list once the timeslots are decided.
- TabAtkins and fantasai will be added as editors to CSS Position
- There was wide interest in allowing trailing commas in many or all functions (Issue #4968: Allow trailing comma in gradient functions (and probably others)).
- Selectors have a higher risk of compat problems so may need to be excluded.
- Media lists of @media will also allow trailing commas.
- Trailing commas will be omitted for serialization.
- Trailing commas only are allowed at the end of a block, not in the middle.
- Since handling trailing commas is something done by some preprocessors research will be done to see the popularity of the functionality.
- TabAtkins will write up proposed text for review and resolution.
- Resolved: Accept the comment at the end of Issue #4946 (editorial: Paint Containment description is incomprehensible)
- “The contents of the element including both the paint of the descendants and their geometry” becomes “The contents of the element including any ink or scrollable overflow”
- “This is as if overflow: visible was changed to overflow: clip at used value.” becomes “The behavior is described in this paragraph is equivalent to changing overflow:visible into overflow:clip at used value time, while leaving other values of overflow unchanged.”
- The above resolution will be added as an errata to Contain L1 once some other editorial items raised have also been resolved upon.
- Resolved: Move what is known as subtree-visibility into CSS Contain L2 (Issue #4843: subtree-visibility CSS property)
- Resolved: Make vmpstr a co-editor of CSS Contain L2
- Resolved: Rename subtree-visibility to content-visibility
- The proposed text to handle scrollbars when intrinsic-width is > width needed to take into account when the scrollbar size is affecting the intrinsic-size. (Issue #4415: Scrollbars when intrinsic-width is > width?>)
Full Meeting Minutes
Minutes Telecon 2020-04-15
- There are currently only a few items tagged for F2F discussion. Unless more items are added soon only one day will be set aside for the virtual F2F.
- The W3C is planning to update their website. Anyone interested is encouraged to participate on the wiki.
- Resolved: Properties that accept quirky lengths accept number token which is converted at parse to pixels (Issue #4874: Quirky lengths and math expressions)
- Resolved: This resolution [above] does not apply to any quirks inside of calc (Issue #4874)
- Resolved: Encourage SVG to follow this approach (Issue #4874)
- Resolved: Let editors choose the behavior and mark this at-risk (Issue #4893: Ogham Space Mark needs to disappear at the end of a line)
- Resolved: Publish new WD of css-text-3
- It may be possible to convert CSS 2 to use bikeshed. Anyone interested is asked to review the github.
- Resolved: Empty ruby containers are sized as if they have empty things in them (Issue #4631: Size and position of empty ruby level containers)
- Resolved: Margins, borders and padding do not apply to ruby base or ruby annotation containers (Issue #4937: Be more specific about the box model of base/annotation container boxes)
- Resolved: Add mark, marktext, and buttonborder colors to system colors (Issue #4924: We should add sufficient system colors to fully implement the HTML UA stylesheet)
Full Meeting Minutes
Minutes Telecon 2020-04-08
- Please add the F2F agenda tag to any github issues which should be discussed. There is a strong need to build an agenda early since this F2F will be virtual. Anyone who objects to the proposed time slots in the members only list needs to reply to the thread shortly so a different window can be found.
- Resolved: Add color-scheme to list of properties affected by forced-colors mode. Forced to value calculated based on colors used (Issue #3885: Add color-scheme to properties affected by forced color mode)
- Resolved: The system colors should have meaning outside of forced-colors and reflect dark and light mode changes (Issue #4883: System colors when NOT forced-colors:active)
- Resolved: Requirement on legible background/foreground colors should be made a should to reflecting WCAG contrast ratio but with exception that it only applies when browser generates default colors (Issue #4883)
- Resolved: Add to previous resolution that user contrast preference must take precedence (Issue #4883)
- Resolved: Move subtree-visibility into CSSWG
- The security/privacy section of the subtree-visibility spec will be filled out and chrishtr will take the lead on having co-authors that aren’t in the working group join up so they can continue their work.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: