Last Call for Comments on CSS Box Sizing Level 3
The CSS Working Group has published an updated Working Draft of CSS Box Sizing Level 3. This and the previous Working Draft published in October incorporate various fixes since the May 2019 Working Draft, and consist mostly of subtle adjustments to CSS’s automatic sizing rules and miscellaneous editorial improvements. Significant changes since the May 2019 Working Draft are listed.
As there are hardly any issues left, we intend to transition this module to Candidate Recommendation following completion of horizontal review. Consider this the Last Call for Comments!
As usual, 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-3]) 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 Candidate Recommendation
The CSS Working Group has published a Candidate Recommendation of CSS Box Model Level 3. This specification describes the CSS box model and the margin and padding properties from CSS2, which create spacing in and around a CSS box. Level 3 contains no new features compared to CSS2; it exists to define terminology on which a number of current CSS modules depend. Consequently, we expect it to advance to REC fairly quickly once any remaining editorial requests are fulfilled. 🙂
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-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Minor Updates to CSS Images Level 3, CSS Grid Level 1, CSS Display Level 3, CSS Backgrounds and Borders Level 3
The CSS Working Group has published minor updates to several Candidate Recommendations:
For the most part, these updates make clarifications and fix minor errors. We have also renamed the “intrinsic dimensions” of a replaced element (such as an image) to its “natural dimensions”, to be consistent with the naturalWidth and naturalHeight interfaces in HTML and to more clearly distinguish them from the layout boxes’ “intrinsic sizes” used in our sizing algorithms (which are usually informed by such dimensions, but are not identical to them).
As usual, 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-images-3]/[css-display-3]/[css-grid-1]/[css-backgrounds-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-12-16
- Resolved: Publish CSS Text 3 as CR
- Resolved: New CRD for Images 3
- Resolved: New CRD for Grid L1
- Resolved: Republish a new CRD for Grid 2
- Resolved: Update Containment 1 REC
- Resolved: Accept the PR and republish WD of containment 2
- Resolved: Move CSS Box Model 3 to CR
- Resolved: Publish a new CR for Backgrounds and Borders 3
- Snapshot 2020:
- Resolved: Move CSS Box Model to the top
- Resolved: Move images 3 to stable bucket
- Resolved: Moving sizing 3 to stable limited test
- Resolved: Color L4– move to stable needs testing
- Resolved: Add grid 2 to snapshot in same place as grid 1
- Resolved: Publish snapshot 2020 as a note
- There has been further discussion about the possibilities for issue #5624 (Higher level custom properties that control multiple declarations) which are summarized in a comment on GitHub. Several of the proposals from the last meeting have been ruled out and more details have been added to the proposal to de-sugar @if into inline if() calls. Discussion will continue on GitHub to look into if there are better ways to handle some difficult cases.
- Resolved: Change css-connected by css created bool where it cannot be unset until removed from a document (Issue #5707: Browsers disagree on what it means for a FontFace object to be “CSS-connected”, and what effect does it have)
- Resolved: Have document.fonts.add when called with CSS created FontFace object throw an error (Issue #5707)
- Resolved: Close no change (Issue #5779: It’s a bit unfortunate that user stylesheets can’t specify arbitrary colors)
- Resolved: Scrollbar colors should compute to auto in forced-colors mode (Issue #5778: scrollbar-color should probably compute to auto in forced-colors mode)
- Resolved: Mark this property at-risk (Issue #4496: Snap area trapping behavior of non scrollable elements)
Full Meeting Minutes
Minutes Telecon 2020-12-09
- The group was in favor of having more long-form meetings since they’re now virtual. Rossen and astearns will propose specific days/times on the private list.
- Due to the change in patent policy, everyone will need to re-join the working group to accept the policy. Emails should go out shortly.
- The PR to change the applies to text was merged (Issue #5303: CSS Text, CSS Fonts, and CSS Text Decor). Any issues or missed specs should be raised as separate issues.
- Issue #5697 (Inconsistent phrasing around placement of @import rules) will be closed as editorial. A new issue will be opened for the naming of the
stylesheet grammar construct.
- leaverou introduced her proposal for fixing the current limitation that custom element authors cannot use custom properties in the place of presentational attributes (Issue #5624: Higher level custom properties that control multiple declarations). There was a lot of interest in solving and some discussion around creating some syntactic sugar and using if() conditions to make it possible. Discussion will continue on the issue.
- Everyone agreed that quirks should not skip grid and flexbox items (Issue #5545: Avoid percentage height quirk in new layout models). There was concern about web compat in making the change, but the group will try for it and revert if there’s breakage.
- Resolved: dholbert to make a change to quirks spec to clarify behavior for flex and grid items and containers (Issue #5545)
- Several browser vendors will go back and check with their teams if there are any concerns requiring a higher number of minimum bits for storing colors in css data structure (Issue #5667: Minimum bit depth for serializing
color() values)
Full Meeting Minutes
Minutes Telecon 2020-12-02
- On the next call the group will decide when to hold our next virtual F2F. Anyone with thoughts in can send them to the private list or come prepared to discuss on the next call
- The group discussed if creating a way to indicate content which is not currently visible should be searchable is a problem they want to solve before going into details of if the proposed content-visibility: hidden-matchable property is the right way to do it. (Issue #5595: Proposal: content-visibility: hidden-matchable).
- The main concern expressed with such a property is that it removes the optimizations allowed by visibility:hidden and display:none and could therefore be expensive to the browser.
- One suggestion to address it was to allow the content which is content-visibility:hidden-matchable to be lazy-indexed instead of being indexed on first load.
- Discussion on this and the rest of the issue will continue on GitHub
- Resolved: Have separate keywords for the visible and contained value vs initial value (Issue #5695: Apply containment on `content-visibility: visible` ; use `normal` as initial value)
- The name of the properties will be discussed further on GitHub and then brought back to the group.
- miriam introduced the current status on the discussion for 1 dimensional container queries (Issue #1031: Do we need size containment in a single dimension to enable container queries?).
- There are two different, and not necessarily mutually exclusive, solutions being discussed:
- The “pinky promise” solution where when you get the width of the container query you say that you won’t do any of the behaviors which would change the width later.
- The “plug the leaks” solution is to address issues as they’re discovered. Currently, there are only two known issues both of which have potential solutions. Given that people have been thinking about this for a while and only found two issues, it’s likely that there aren’t many more leaks which are unknown.
- Both solutions were discussed and both could be viable solutions. Discussion will continue on GitHub.
- Resolved: Invalid path strings make the syntax invalid at parse time (FXTF Issue #392: The computed value of offset-path: path(‘ ‘))
- Resolved: Empty path is considered invalid (FXTF Issue #392)
- The desire with spelling-error and grammar-error is to create some spec text which says UAs may take steps to prevent fingerprinting and give disallowing loading external resources as an example. Fantasai will draft up sample language for the group to discuss and resolve on. (Issue #5731: Privacy considerations for external resources)
- Resolved: The contain-intrinsic-size property takes 4 longhands, logical and physical, which have a normal value (Issue #5432: Allow specifying only one dimension for intrinsic sizing)
- A separate issue will be opened on github about if there is value in defining a ‘none’ property for contain-intrinsic size.
Full Meeting Minutes
Minutes Telecon 2020-11-18
- Many of the use cases addressed in PR #5677 (Add notIfViewed to ScrollIntoViewOptions; add FocusScrollOptions) were handled in the Scroll Snap spec so zcorpan will review and open an issue if anything is missing. There may also be a need to reference Scroll Snap in CSSOM View so that the relationship is clearer to authors and implementors.
- Resolved: Change the PR to just if-needed bits with a reference to scroll snap as long as it’s handling the use cases (PR #5677)
- The resolution to only allow appearance:button on buttons (Issue #5147: Change appearance: button to only apply to buttons) and have it behave the same as appearance:auto was re-opened from a request to be able to have link elements also be styled as buttons.
- Some members were arguing that this is not about styling but about a desire to have buttons able to do more link-like things and therefore this should be discussed within the WHATWG.
- Another argument was that part of why the desire to style links as buttons didn’t come up before is that the native form control styling is too limited and therefore this should be covered in OpenUI.
- The third argument is that this is specifically a request about styling and therefore the request to allow links to be styled as buttons is a logical extension of the property.
- Resolved: Close this issue no change and open a more narrowly scoped issue (Issue #5147)
- Since the last time the group discussed issue #5595 (Proposal: content-visibility: hidden-matchable) there was discussion on GitHub about the accessibility concerns raised on the call and the concerns have been resolved.
- smfr will further look into how Safari is indexing pages to see if that’s a valid use case for the proposed property.
- There is a concern with the current proposal having a difference in behavior between fragments which would cause confusion. Discussion will continue in the issue to try and resolve it.
- On the next call (in two weeks) the group will start by discussing on if this proposal is something which should continue being pursued.
Full Meeting Minutes
Updated CSS Lists and Counters Level 3
The CSS Working Group has published an updated Working Draft of CSS Lists Level 3. This module contains CSS features related to list markers and counters: styling them, positioning them, and manipulating their value.
This update refines the definition of which properties apply to ::marker and improves counter scoping and inheritance to be compatible HTML list numbering. Changes since the last Working Draft are listed in the Changes section.
Much of this module, particularly features necessary to support HTML list numbering via CSS counters, is now implemented in Gecko and Blink. The next phase will be mostly refining what’s already there in preparation for CR, with significant new work (including details of outside marker layout) being pushed to the next level.
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-lists-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-11-11
- There were concerns about trying to remove the actual value of colors from the getComputedStyle return (Issue #5710: Shielding system colors to avoid fingerprinting) so much of the group was leaning toward no change and documenting the fingerprinting risk. However, the group is going to wait a week before resolving to allow for checking with privacy teams.
- Resolved: Republish a new WD of Fonts 4
- The group discussed the proposal to add currentBackgroundColor to Color 5 (Issue #5292: Add `currentBackgroundColor` Variable). The use case is to make it easier to have style elements like borders be defined based on their background color. During the conversation there was a fair amount of implementation complexity uncovered since there is often transparent background values. Discussion will return to github to determine if the benefit outweighs the implementation complexity as well as dive further into the detailed requirements.
- Resolved: For quirks mode only, the scrolling element should follow same propagation as the overflow:clip (Issue #5601: Document.scrollingElement doesn’t reflect viewport propagation correctly in presence of overflow: clip)
- Resolved: No change to the viewport size calculation (Issue #5260: No way to access the viewport size without losing precision)
- emilio will experiment with allowing the viewport size to return doubles to see if it really causes the compat issues which lead to the above resolution. If there aren’t compat issues he’ll re-open the issue. If there are compat issues he’ll create a new issue to develop a separate API to return the doubles.
- In order to define how rounding should function in CSS (Issue #5689: Is `round` special in CSSOM?) requires a conversation around which is the best language to match. Discussion will continue on GitHub until there’s a more definite proposal.
- Resolved: Have different interfaces for declarations blocks that expose a different set of descriptors/properties (Issue #5649: The way CSSStyleDeclaration exposes properties is not ideal)
- Resolved: Publish a new WD for Values 4
Full Meeting Minutes
New Working Draft of CSS Values & Units 4 Published
The CSS WG has published an updated Working Draft of CSS Values & Units Level 4. This specification defines the CSS property definition grammar, and the value types that are common across many specs, such as <number> or <string>.
Significant changes since the previous (2019) Working Draft are listed Changes section. New to this draft is:
- the definition of the <ratio> type, factored out from the
aspect-ratio media query and re-used in the new aspect-ratio property in CSS Box Sizing Level 4.
- the introduction of a large number of new math functions, such as
round(), sin(), pow(), and some accompanying numeric constants
- a new
src() function, which is identical to url() but requires quoted strings (which makes it possible for it to take functions that evaluate to strings, such as attr() or var()).
- a substantially revised definition of the
attr() function (with some substantial pending issues)
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-values-4]) 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: