CSS WG Blog front page
Minutes Telecon 2020-06-24
- There was proposal for simplifying the solution to issue #4178 (More granular overriding of forced colors mode than per-element) by allowing system-colors to stay in place for forced-color mode. However, one of the primary motivating cases was to allow an arbitrary color. This case will be better captured in github and discussion will continue there.
- Resolved: Have color scheme use the same
meta scheme as theme color. (Issue #3846: What happens with multiple metas?)
- Resolved: Ask HTML to specify this and move out of CSS specs (Issue #3846)
- Resolved: Specify we use host document behavior for URL types in
attr() (Issue #5079: attr()‘s url type seems wrong)
- Resolved: Do testing in this area and specify values for this case (Issue #3800: Precisely define which media features an undisplayed page has)
- In general the group liked the idea of returning default defined data but webcompat needs to be maintained for existing values.
- Future media queries should have defaults defined in the spec to prevent issues in the future.
- Resolved: Remove at-risk on these [hover, any-hover, pointer, and any-pointer] media features (Issue #1989: Interaction media features (any-pointer, etc) still at risk?)
- Resolved: Change the fallback value for space-around and space-evenly to safe center (Issue #5088: Content-distribution keywords that fall back to “center” can’t be made safe)
- Anyone with interest in security or attr() was asked to review and help solve the security concerns raised in issue #5136 (Hide “sensitive” attributes from CSS)
Full Meeting Minutes
Updated WD of CSS Inline Layout L3
The CSS Working Group has published another updated Working Draft of CSS Inline Layout Level 3. This module describes the block-axis alignment and sizing of inline-level boxes and text. It also adds a special layout mode for drop caps and similar initial letter styling.
This is another significant update which restructures some of the new features added earlier, pulls in the remainder of the relevant CSS2 (and CSS Writing Modes) prose, restructures the vertical alignment chapter, and integrates all the new features together with the line layout rules.
The draft now also includes a high-level description of the inline layout model and imports prose from CSS2 defining how line heights are calculated.
All significant changes since over the last two updates are listed in the Changes section.
There remain plenty of open issues, but at this point the draft is substantially complete: now would be a good time for high-level reviews. (Remaining issues are largely working out layout details and internationalization problems.)
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-inline]) 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-06-17
- Resolved: Accept change as proposed by fantasai [move top|bottom|center values from alignment-baseline to baseline-shift] unless strong impl argument (Issue #5180: Shift top | bottom | center values from alignment-baseline to baseline-shift)
- The group looked at several diagrams in order to understand the proposal to handle line-sizing and leading-trim (Issue #5168: Rethinking line-sizing and leading-trim). They were a drawing from dauwhe and a slideshow from fantasai. Slide 52 was recreated on a whiteboard and discussed in detail to reach a common understanding of the proposal.
- The proposal was well received and was an improvement over the existing behavior using line-height.
- There were some open questions which need to be answered prior to the spec being finalized:
- Determine if the spacing should use just the leading in the content’s line box or also have the assumed gap which includes the leading on adjacent line boxes.
- When looking at font metrics should this look at first available font or at the whole font family. First available gives more control to designers but the whole font family makes it less likely to get overlap when a fallback happens so might be a better default.
- Need to make clear that this doesn’t impact the line box model.
- Should this be two properties as proposed or one property that takes one or two values.
- Resolved: Adopt new model described in the issue, continue working on it (Issue #5168: Rethinking line-sizing and leading-trim)
- Resolved: Apply negative half leading to margin box edge (Issue #5178: line-height < 1 in a margin-box line layout model)
- Resolved: Define the central baseline so if the font has an explicit ideographic central baseline, use that. If not, use halfway between ideographic top and bottom. If that’s missing, halfway between ascent and descent (Issue #5177: About the central baseline)
- The text for issue #1254 (‘line-height: normal’ definition should reflect reality of determining based on fonts) needs to be reviewed but will stay in the spec as-is for now.
- Resolved: Publish updated working draft of CSS-Inline
Full Meeting Minutes
Minutes Telecon 2020-06-10
- While discussing how to handle length video-* features (Issue #5044: length units in video-* media features) the group spent time working out what the use cases are that lead to this request.
- The conclusion was that the use case to know the dimensions was very similar to the discussion that led to srcset. There are possible fingerprinting vectors when exposing this data which need to be carefully considered.
- Additionally, there were some questions as to if this was properly a media query or should change more to be UA driven to decide what content to serve.
- A call will be coordinated between the CSSWG and the Media WG with representation from TAG in order to dive into these questions further.
- Issue #5043 (Definition of video width and height) is related to issue #5044 so will also wait on the coordinated call before a resolution can be reached.
- Resolved: We switch dialog positioning to rely on centered fixed container with max-height and overflow:auto pending use counter data (Issue #4645:
dialog positioning should be describable in CSS)
- Resolved: Do not honor non-URL background images in forced color adjustments (Issue #4916: Should probably not honor non-url background images)
- There was interest in looking into a more nuanced solution to issue #4916 using the alpha channel.
- Resolved: Add the forced value to prefers-contrast (Issue #3856: Fold `forced-colors` and `prefers-contrast`?)
Full Meeting Minutes
Updated Working Draft of CSS Overflow Level 3
The CSS Working Group has published an updated Working Draft of the CSS Overflow Module Level 3. This module contains the features of CSS relating to scrollable overflow handling in visual media. This level is focused on completing a precise specification for the existing overflow features, including the overflow property and its longhands; line-clamp, its longhands, and its legacy pre-standard syntax; and the text-overflow property. A few additional features introduced in support of the CSS Containment Module are also defined: overflow: clip and the overflow-clip-margin property.
It has been quite a while since the last update, so there is a fair amount of changes. The main changes can be broadly grouped in 3 categories:
- More details about what is and isn’t included in the scrollable overflow of a box. These changes are driven by trying to find the best balance between desirable behavior and compatibility constraints.
- Significant revisions to the definition of the
line-clamp property and its longhands. The behavior is more precisely defined, takes into account ease-of-implementation concerns raised by interested browser vendors, and covers compatibility with the pre-standard -webkit-line-clamp property. Implementation experience is still limited, but the design is considered roughly complete. Detailed review and feedback is strongly encouraged at this point.
- Introduce the
overflow-clip-margin property, which determines how far outside its bounds the element is allowed to paint before being clipped when using overflow: clip or the related contain: paint from the CSS Containment Module.
See the Changes section for further 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-overflow-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated CSS Containment Level 2 Working Draft
The CSS Working Group has published an updated Working Draft of the CSS Containment Module Level 2. This CSS module describes the contain property, which indicates that the element’s subtree is independent of the rest of the page, and the related and content-visibility property. This enables heavy optimizations by user agents when used well.
The main changes brought by this update are defining the interaction between paint containment and the newly introduced overflow-clip-margin, and adding the content-visibility property. The content-visibility property controls whether or not an element renders its contents at all, along with forcing a strong set of containments, allowing user agents to potentially omit large swathes of layout and rendering work until it becomes needed.
See also the Changes section for further 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-contain-2]) 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-06-03
- The working group will update the wording for publishing a WD without a resolution from requiring exact wording to be approved to having appropriate review for the wording.
- Resolved: Use vs in color-contrast function (Issue #5087: color-contrast needs another comma)
- Resolved: Remove the special case of background images on input elements wrt forced colors (Issue #4917: Why special-casing background-image for inputs?)
- Resolved: Publish css-inline
- This publication will include the draft ideas for line-box-contain (Issue #3199) though the issue will stay open until all details are agreed upon.
- Resolved: Rename initial-letters to initial-letter (Issue #862: Should `initial-letter` be plural?)
- Resolved: Atomic inline initial letter size as regular atomic inlines, except for auto sizes being calculated using the initial letter algorithm (Issue #3231: Sizing atomic inlines as initial letters)
- Resolved: shape-margin and shape-outside apply to initial letter wrapped inline boxes, modifying or replacing the shape of the glyph (Issue #5117: shape-margin on initial-letters-wrap: first)
- Resolved: Add definitions for paged and continuous media to MQ4 (Issue #5091: Define Media Groups: continuous vs paged, etc.)
- Resolved: No change to @media width/height (Issue #4713: CSS media query width and window.innerWidth may not be equal)
Full Meeting Minutes
Updated Media Queries Level 5 Working Draft
The CSS Working Group has 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.
This update adds a set of media features specific to devices with a separate “plane” used to render videos, as well as one to inquire about the dynamic range of a device.
This comes on top of various media features added since Media Queries Level 4 by the earlier First Public Working Draft of Level 5:
* A set of media features (prefers-reduced-motion, prefers-reduced-transparency, prefers-contrast, prefers-color-scheme) to let authors respond to various preferences expressed by the user.
* forced-colors, a media feature to detect the fact that the User Agent has forcibly applied to the page a user-chosen color scheme.
* A section on custom Media Queries, and two media features (light-level and inverted-colors) that had been dropped from Level 4 when publishing it as a Candidate Recommendation.
All significant changes 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 ([mediaqueries-5]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
Updated CSS Inline Layout Level 3
The CSS Working Group has published an updated Working Draft of CSS Inline Layout Level 3. This module describes the block-axis alignment and sizing of inline-level boxes and text. It also adds a special layout mode for drop caps and similar initial letter styling.
This is a significant update which pulls in some major new features, including control over whether to use a box’s first/last line’s baseline for baseline alignment (baseline-source) and new proposals for altering how line heights are calculated and for controlling leading (line-sizing and leading-trim, currently). Note that these proposals are in early drafting stages and are expected to change significantly.
The draft now also includes a high-level description of the inline layout model and imports prose from CSS2 defining how line heights are calculated.
All significant changes since the last Working Draft are listed in the Changes section.
Plans for the next update include working on major design questions on line-sizing and leading-trim (possibly redesigning them significantly), filling out missing details on how vertical-align and related features actually work (copying from CSS2), and describing more rigorously the initial letter layout model.
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-inline]) 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-27
- Resolved: Deprecate ‘speech’ and have it have the same behavior as other deprecated MQs (Issue #1751: Deprecate ‘speech’ media type as well?)
- Resolved: Put dynamic-range and video-* in MQ L5 (Issue #5042: Which levels should the dynamic-range and video-* media features be in)
- Resolved: Remove the no-preference value (Issue #3857: UA guidance on light vs no-preference)
- Resolved: Add a note that no-preference used to exist but was removed due to lack of implementations (Issue #3857)
- Exposing the browser styling for selection/inactive-selection (Issue #4579) requires first defining what the browsers are doing. On the call there was exploration of Firefox’s behavior. More details of testing as well as webkit behavior information will be added to github in order to further discussion.
- Resolved: Close issue #5005 (Physical inset properties), add a note to the spec trying to explain the confusion
- Resolved: Make the proposed change to make processing of ruby only work on in-flow content (Issue #4958: siblings/children vs in-flow siblings/children in box fixup)
- In order to address image support for column rules in multicol (Issue #5080) there needs to be a solution for all layout modes so that the solution doesn’t block any use cases. Discussion on a design will continue on github.
- Resolved: Remove ‘only’ keyword, simplify the table, add a note about dropping only (Issue #3881: Limits on the `only` color scheme keyword)
- Resolved: Remove at-risk label on ‘anywhere’ value of line-break (Issue #5072: The ‘anywhere’ value of line-break)
- Resolved: Close no change (Issue #4993: Should enclosed counting rods / tai xuan jing / yi jing hexagrams be space-discarding?)
Full Meeting Minutes
Archives
Browse by date:
Browse by category:
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact:
