CSS Grid Layout Level 2 (Subgrid) Candidate Recommendation
The CSS Working Group has published a Candidate Recommendation and invites implementations of CSS CSS Grid Layout Level 2. This module defines a layout manager, the grid, which makes it easy to specify complex, responsive 2-dimensional layouts for a page or sub-component of the page. Level 2 introduces the “subgrid” feature that was cut from Level 1 due to lack of implementations, and which allows sharing grid lines across nested markup.
There have been no changes since the previous Working Draft other than incorporating the full text of CSS Grid Layout Level 1; and all new features other than subgrid have been deferred to Level 3.
The editors are grateful to Mozilla for implementing and giving feedback, and encourage other CSS implementations to update so that authors and users can benefit from subgrid’s ability to combine content-sized grid layouts with nested structural markup.
Feedback can be sent 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-2]) and your comment topic in the subject line.
CSS Grid Layout Level 1 Revision 3
The CSS Working Group has published an updated Candidate Recommendation of CSS Grid Layout Level 1. This module defines a new type of layout manager, the grid, which makes it extremely easy to specify complex, responsive 2-dimensional layouts for a page or sub-component of the page.
This update addresses most of the feedback received since the December 2017 CR, including almost all of the known errors; there remain a number of issues relating to improvements to track sizing algorithm that will be addressed in the next revision. The changes consist mostly of slight adjustments to the grid sizing algorithm and a few fixes to things like serialization. All significant since the last Working Draft are listed (with diffs) in the Changes section, and a Disposition of Comments (102 issues) is available.
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-grid-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 2020-08-19
- Resolved: Reject proposal, no change to semicolons (Issue #5413: Voluntary semicolons)
- Implementors are requested to review the proposal to alter how ratio-constrained elements are sized in definite-sized Grid/Flexbox containers (Issue #5317). The proposal is to contain-fit the image into the available space instead of the current behavior in the spec which is to calculate its max-content size using the inline axis of the containing block.
- Resolved: System colors will be accepted as specified, everything else is forced (Issue #4178: More granular overriding of forced colors mode than per-element)
- In response to the working group’s request for a more detailed proposal a possible spec was written for review (Issue #5187: Allow specifying the “accent color” of a form control element).
- The general approach to let an author define what the accent color should be and then additional colors was generally accepted.
- The proposal has a mapping for each form control to which color is ‘primary’ and which is ‘contrasting’. There is a request to have more examples of each form control including historic designs to make sure the mapping holds up. There was also a question about how gradients would be handled.
- The biggest concern expressed is that being too exact in the definition will limit future variations on form controls. The proposal was written to be extensible but the exact mapping may still impose constraints. There will need to be a balance between defining too much and creating limitations in the future versus defining too little and having authors not want to use the property or everyone have to conform to the first implementation.
- There wasn’t time on the call to develop next steps for this proposal so it will be at the top of next week’s agenda.
Full Meeting Minutes
Minutes Telecon 2020-08-12
- The current proposal for TPAC is to meet the week of 19 Oct. Unless an objection is raised on the private list that’s what will be submitted later this week.
- On next week’s call the group will discuss the proposed cascade layers syntax. Everyone is encouraged to review the proposal in advance.
- Resolved: Publish new WD of Worklets
- Resolved: Hand over worklets to HTML after publishing the WD (Houdini Issue #1000: Merge the worklets spec into HTML?)
- ‘prefers-contrast: high’ media feature:
- The group agreed that there were potential use cases for more than one value for higher contrast preferences so the solution selected needed to be able to handle more than a single value in the future. However, it was too early to add any other values now.
- Within issue #2943 it was also mentioned that there weren’t enough use cases listed to help understand the intent behind the prefers-contrast property. AmeliaBR agreed to lead ensuring the use cases are all in spec.
- Additional concerns were raised about ‘prefers-contrast: forced’ and ‘forced-colors: active’ being duplicated properties and a separate issue will be added to github to discuss further.
- Resolved: Change ‘high’ and ‘low’ in the MQ to ‘more’ and ‘less’ (Issue #2943: `prefers-contrast: high` media feature doesn’t account for macOS and iOS)
Full Meeting Minutes
Minutes Telecon 2020-08-05
- Resolved: Shift shadow dom cascade to cascade 4, remove scoping from cascade 4, move cascade 4 to WD and republish (Issue #5372: Define Shadow Tree in Cascade)
- Resolved: Make forced-color-adjust not animatable (Issue #5342: Animation type of forced-color-adjust)
- Resolved: Non-0 height as a result of aspect-ratio disables margin collapsing between top and bottom (Issue #5328: Should we mention aspect-ratio in margin collapsing?)
- Discussion will continue on Issue #5342 about how to handle margin collapsing when the height is 0.
- There’s still some questions on expected behavior for issue #3949 (Switch to opt into transparent canvas for additive displays) so discussion will continue on github.
- fantasai will draft proposed spec text for the group to review which will state that text-transform being a CSS property is not intended to convey semantics. If you’re using an accessibility API it may take aspects of presentation into account but text-transform should not be used for semantics. (Issue #3775: text-transform’s design, intent and reality resolution)
- The group explored adding a ::punctuation pseudo class in order to handle the need to style punctuation differently when it’s in a ::first-letter (Issue #2040: Problems with styling ::first-letter with punctuation).
- If going with this approach it would be scoped to tree-abiding punctuation.
- There is a need to be able to style the punctuation before the first letter differently than after the first letter so this proposal will need to be able to select between before and after. People were okay with scoping so being able to do a different style for two punctuation marks before the letter would be out of scope.
Full Meeting Minutes
Minutes Telecon 2020-07-22
- There is a page to vote on and suggest statistics to be gathered as a part of the HTTPArchive Web Almanac. Group members are requested to participate and suggest items which would help in specification writing
- Examples were added for using ::first-letter and spaces (Issue #5154: ::first-letter should include space separators). There are also examples where a space is used to ensure only a punctuation mark and not the letter receive the ::first-letter style so a switch may be required. This will be added to the F2F agenda since not everyone interested was available for today’s call.
- Resolved: Reject [phi] for now and if data shows up from HTTPArchive that it is fairly common we re-open and put it in (Issue #4702: Math Constant phi for Golden Ratio)
- masonfreed presented the study and conclusions for controlling the color on form controls. The conclusion was that there would need to be two colors exposed; foreground and background.
- There was concern that range and progress bar were excluded from the proposed spec text and investigation will be done as to how they can also respect the new values.
- The proposed properties include ‘foreground’ and ‘background’ which implies that a certain level of contrast should be encouraged. This may be good, but needs to be thought through more since not all form controls have contrast right now.
- The proposed spec text is vague in terms of details due to the current incompatibility around form controls. However, the group felt it should be more specific so that discussions do happen prior to one browser implementing and everyone getting locked into that approach.
- There was interest in having the openUI group also define what is foreground and what is background. Several members of the group expressed an interest in seeing a demo/overview of the openUI work.
- An additional concern was to make sure whatever is specified will be able to accommodate future innovations in look and functionality of form controls.
- masonfreed will add to the proposed spec text more specificity about implementation and than bring it back to the group.
Full Meeting Minutes
Updated CR of Media Queries L4 and WD of Media Queries L5
The CSS WG has published an updated Candidate Recommendation and invites implementations of Media Queries Level 4. It has also published an updated Working Draft of Media Queries Level 5.
Media Queries allow authors to test and query values or features of the user agent or display device, independent of the document being rendered. They are used in the CSS @media rule to conditionally apply styles to a document, and in various other contexts and languages, such as HTML and JavaScript.
Level 4 brings significant improvements to the syntax, and refocuses Media Queries away from categorizing devices into exclusive media types, and instead introduces a broad range of media features, to enable authors to inquire about various aspects of the environment the web page is being rendered into. This include the viewport’s geometry, information about the color capabilities, the input devices, and a few more things.
This new Candidate Recommendation is a fairly minor update from the previous one. The main changes are documented in the Changes section. A Disposition of Comments is available.
Level 4 is considered fairly stable at this point, with no known issue. The CSS Working Group encourage User Agents to continue implementing it, and is looking for feedback from these implementers and early users of its features.
Level 5 builds upon this foundation, adding a few more media features to look into things like the dynamic range of the display, whether the rendering environment is capable of running scripts, or whether the content is rendered on an opaque or transparent screen. It also explores a few new areas:
- enabling authors to create custom media queries
- media features related to devices with a dedicated video rendering plane
- a set of media features focused not so much of the capabilities of the device, but rather on the preferences of the user.
Details of changes since the previous Working Drafts, as well as between level 4 and 5 are listed in the Changes section.
The features introduced Level 5 are much more experimental, and the CSS Working Group encourages broad discussion of their benefits and downsides. Participation in the discussion of existing unresolved issues is most welcome.
Please send feedback on either documents by filing an issue in GitHub, including [mediaqueries-4] or [mediaqueries-5] in the title of the issue as appropriate.
Alternatively, you may also send a mail to the (archived) public mailing list www-style@w3.org with the spec code ([mediaqueries-4] or [mediaqueries-4]) and your comment topic in the subject line.
Minutes Telecon 2020-07-15
- There will be 4 4-hour F2F timeslots the week of July 27th. Details are on the private list. Please begin to tag any F2F agenda items on GitHub. If you have a preferred day or timeslot use the milestone to indicate that.
- A joint session with the media working group was held to discuss the video media queries. Though they heard the CSSWG’s concerns about the solution they still believe that the best way forward is the proposed media queries. Discussion will return to github on issue #5044.
- Resolved: Mark Update media feature at-risk in MQ4
- Resolved: Update CR of MQ4
- Resolved: Republish WD of MQ4
- Editors are reminded to stay on top of PRs as old PRs have merge problems. (Issue #5314)
- Most of the group agreed the the proposal for ::first-letter to include space separators (Issue #5154) however there was an objection based on a lack of real world examples. Examples will be gathered and then discussion will continue.
- Resolved: grid-template-areas should not accept empty strings (Issue #5110: Should grid-template-areas accept empty strings?)
- Resolved: Accept edits to spec for explicit grid (Issue #4914: Does grid-template-areas really expand the explicit grid?)
- Resolved: Add ::marker { text-transform: none; } to UA stylesheet, at least for now (Issue #4206: Does text-transform inherit to ::marker?)
- Resolved: text-transform applies to ::marker (Issue #4206)
- There wasn’t enough time left on the call to reach a resolution for issue #5120 (initial-letters-wrap: first, whitespace collapse needs defining) but everyone who spoke was in favor of discarding the space when there’s a drop-cap and keeping with raised-cap. Unless there’s objections raised in github a resolution will be called for next week.
Full Meeting Minutes
Minutes Telecon 2020-07-08
- Resolved: Publish Color 5 once #4711 (color-mix to allow more than two colors?) is edited in and there’s a major changes list
- A virtual F2F is being planned around the time that the in person F2F was originally scheduled. Group members are encouraged to participate in planning on the private mailing list.
- Resolved: Min-content and max-content keywords represent size of element at top and bottom extremes of fit-content or shrink-to-fit sizing and therefore match size it would take under a min or max constraint when taking aspect-ratio into account (Issue #5032: Should aspect-ratio affect the intrinsic size?)
- fantasai will evaluate the layout specs and analyze what should and shouldn’t be aspect-ratio dependent. With that analysis she will propose terms to add to the specs which would define the two concepts. She’ll also open a new issue to determine if these two concepts need to be keywords too (Issue #5032).
- If a keyword is created current name suggestions are contain-intrinsic-size and natural-size
- Issue #3268 (Rethinking how to prevent overflow in a container with an explicit aspect ratio) may need to be re-opened to reconsider what the default value should be.
- Another issue will be opened to define in spec exactly how transferring size should happen and if the content-based size goes through the aspect-ratio.
- Resolved: Drop the [
overflow-block:optional-paged] value with a note explaining why (Issue #5287: Drop overflow-block:optional-paged)
Full Meeting Minutes
Minutes Telecon 2020-07-01
- Resolved: Make from-image’s none value apply to background and any other images (Issue #5245: Clarify which images image-orientation applies to)
- Resolved: Publish a version with all keywords but ‘longer’ (Issue #4735: When mixing hue, there are two ways round the hue range)
- There was wide interest in trying to specify a color for the accent color of form controls (Issue #5187: Allow specifying the “accent color” of a form control element) however there were some concerns about if it’s possible.
- Specifying form controls is being looked at by several people and this was a small step toward that which needs to be compatible with larger efforts.
- Maintaining appropriate contrast may be hard if the accent color is sometimes against background and sometimes against foreground or text.
- The solution needed to work with all existing browser/OS combinations and also support OSs that don’t have accent colors so it is important to do more research before proceeding with moving into spec text.
- Resolved: Accept proposal (Issue #5151: Should aspect-ratio be used for abspos `top: 0; bottom: 0;`?)
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: