Minutes Telecon 2021-09-15
- Resolved: Adopt if/else as next level of css-conditional (Issue #6520: Nesting @supports inside @font-face / font tech queries)
- Resolved: Accept the PR (Issue #6520)
- There are still some open questions and concerns around issue #6520 that were discussed on the call, but they will be raised as separate issues.
- Resolved: Transition css-multicol-1 back to CR (Issue #6612: New CR?)
- Resolved: Add a note [this falls out from the computed value definition] (Issue #6586: What is the serialization “background-position: top right 10px”?)
- Resolved: Serialize as url(“”) (Issue #6447: Serialization of empty url() undefined)
Full Meeting Minutes
Minutes Telecon 2021-09-08
- There are calls scheduled with i18n and a11y on 20th and 27th. Please tag Agenda+TPAC on issues that should be discussed during those calls.
- Please review the updated spec text for Positioned Layout 3. Next week there will be a request for republication.
- Resolved: Close no change: taking BR out of flow removes its effect on the surrounding content, just like every other element (Issue #5749: What is the behavior of an absolutely-positioned
br?)
- Resolved: Reference DOM’s definition of invalidity for static ranges for highlight API (Issue #5497: Invalidation of Static Ranges)
- Resolved: Republish Highlight API
- Resolved: Retitle CSS Scrollbars to CSS Scrollbar Styling (Issue #6549: Improve title)
- Resolved: Republish CSS Scrollbar Styling
- Resolved: Move css-color-adjust-1 to CR
- If a decision isn’t reached on issue #5469 (Should forced-colors override `border-image`?) before the CR publication it will be noted inline as an open issue.
- Resolved: Add marquee to compressible elements (Issue #6342: Add
marquee to list of compressible elements)
- chrishtr will take the lead on reviewing the differences between Gecko and Blink implementations of hit testing. There is still no volunteer to try and specify hit testing, but the group would be interested in doing so if anyone does step forward.
Full Meeting Minutes
CSS Display Level 3 updated to include ‘order’ and ‘visibility’
The CSS WG has published an updated Candidate Recommendation of the CSS
Display Module Level 3. This module describes how the CSS formatting box tree is generated from the
document element tree and some properties to control the type, order, and visibility of those boxes. This update:
All significant changes since the last CR are listed at in the Changes section, and a disposition of comments since the last CR is available.
Please review the draft and 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-display-3]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
It is our intention to post an updated CR Snapshot of this module as soon as horizontal review is completed.
Minutes Telecon 2021-09-01
- Resolved: Add fantasai and chris as editors for Conditional L4
- More volunteers are needed to create short videos for TPAC. The deadline to volunteer is 15 September.
- Resolved: scroll-snap-align and future 2-axis properties use the logical model (Issue #2988: ‘overflow’ 2-value syntax is in wrong order)
- Issue #2971 (Confirm interaction of positioned elements and continue:discard) needs more feedback from implementers familiar with the fragmentation model in order to reach a decision.
- Resolved: Expand the color stop hint grammar with easing functions and define how gradients respond to that (Issue #1332: Add easing functions to color stops)
- Another issue will be opened to explore if we should continue to have smart interpolation of gradients given they have no implementations and add complexity to the above resolution.
- Resolved: Move the work miriam has done to cascade L6 (Issue #5809: Proposal for light-dom scoping/namespacing with re-designed @scope rule)
- Resolved: Take the css-shadow-parts and css-scoping drafts, integrate them, and republish as css-shadow
- Resolved: We are going to start specifying a no motion at all mode that makes motion inducing animations discrete between keyframes where keyframes are sufficiently separated in time (Issue #5321: TAG feedback: interaction with prefers reduced motion)
- Once the no motion mode property is more fleshed out the group will return to the discussion about how to create Media Queries around the new property.
Full Meeting Minutes
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:
- Reserve the CSS-wide keywords for future use in layer-names.
- Clarify that @layer rules respect global conditional rules, but are always applied to the layer order when declared in non-global conditions such as a container query.
- Clarify that name-defining at-rules follow layer order for collision resolution, similar to specificity resolution.
- Disallow interleaving of @layer with @import or @namespace rules.
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.)
CSS Scrollbar Styling Last Call Working Draft
The CSS Working Group has published an updated Working Draft of CSS Scrollbar. This CSS module defines properties to influence the visual styling of scrollbars, introducing controls for their color and width.
Having addressed all outstanding comments, we expect to take transition to Candidate Recommendation after completing horizontal review. So please consider this the last call for comments prior to CR! 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-scrollbars-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-08-25
- Resolved: content-visibility:hidden prevents scrollIntoView and similar functionality from working on the subtree (Issue #6529: Should scrollIntoView scroll to content-visibility: hidden subtree elements)
- Resolved: When an author uses a static range for highlight API, it should actually be a static range internally, not backed by a hidden live range (Issue #5497: Invalidation of static ranges)
- Resolved: Publish a new Highlight API WD when changes [above] are made
- Resolved: @layer statements must occur before or after all @imports, not interleaved (Issue #6522: Proposal to disallow interleaving of @layer and @import rules)
- Based on the TAG feedback on extending the format() syntax for ‘src’, work was done on supporting font-tech queries in @supports. There were several people expressing support, but some concerns around font-families combining and not having an else syntax or inline/nested supports. The group will return to the topic next week to try and reach a resolution (Issue #6520: Nesting of @supports inside @font-face and font technology feature queries).
Full Meeting Minutes
Minutes Telecon 2021-08-18
- Resolved: Return empty style if string begins with a colon, return element style otherwise (Issue #6501: Throwing on invalid pseudo-elements in getComputedStyle is not web-compatible)
- Resolved: Accept edits (Issue #6253: Shorthands should serialize as empty string when longhands have variables)
- Resolved: overflow-clip-margin uses the same corner-adjustment formula as margin/etc (Issue #5896: overflow-clip-margin + border-radius continuity adjustment)
- Resolved: Accept dbaron’s editorial feedback about making the “accidental” case more explicit (Issue #5896)
- Resolved: Serialize specified value of display using keywords specified (Issue #5575: Should display-legacy values be aliased at parse time?)
- Resolved: Close wontfix (Issue #4022: display:contents list-item)
- Resolved: Close no change (Issue #3998: The ‘flow’ keyword is redundant)
- Resolved: Publish new CRD of css-display-3 (after today’s edits) (Issue #6516: Horizontal review)
- Though the group ran out of time for discussion, the expectation is that next week the we be able to resolve issue #4597 (Invalidation of Static Ranges) as close no change.
Full Meeting Minutes
Minutes Telecon 2021-08-11
- Resolved: Spec content:none as having no effect on elements (Issue #6503: Implementing content:none on elements is not web-compatible)
- Resolved: Add perspective(none) (Issue #6488: After #6320 there’s no way to get an identity transform for interpolation of perspective)
- The group is aware of the outages of the drafts server. There’s a proposed solution and work is being done to find time/funding to implement it.
- Resolved: Clamp automatic minimum size of compressible elements, and the transferred size suggestion of non-compressible aspect-ratio elements (Issue #6278: Replaced elements canvas, img, etc should behave as expected when styled with relative sizes in grid, transferred size should not affect them unless specifically asked to)
- Resolved: Close no change (Issue #5566: Resolution of percentage row tracks and gutters with indefinite height)
- Resolved: Accept proposal (Issue #6123: For the Accessibility API visibility:visible within visibility:hidden is problematic)
- Proposal:
- Import ‘visibility’ from CSS2 to css-display-3 (since it is currently only defined in CSS2).
- Define impact of visibility: hidden similar to display: contents (shouldn’t strip necessary a11y information from the tree).
- Add a warning to authors that marking a required structural parent box as invisible while descendants are visible (e.g. table-row invisible while table-cell is visible) can be problematic.
Full Meeting Minutes
Minutes Telecon 2021-08-04
- Resolved: Promote scrollbar-gutter to CSS Overflow L3
- Resolved: Undo previous resolution. Explicitly mark inline-end padding of block container scrollers as undefined in the draft for now (Issue #129: Clarify padding-bottom in overflow content)
- Resolved: Republish masking-1 as CR Draft (FXTF Issue #431: Republish masking-1 as CR Draft)
- Resolved: Publish Colors 3 as updated Recommendation with Candidate Corrections (Issue #6486: Publish updated Recommendation with Candidate Corrections)
- Resolved: Revert previous resolution and allow any ranges to be added to a registry. At paint time we only use ranges that are with the originating document (Issue #6417: Specifying behavior for Highlights involving multiple documents)
- Resolved: Conditionals nested into style rules have their contents parsed the same as style rules (so raw properties are allowed) (PR #6483: Allow conditional nested rules to adopt context)
- Resolved: When we have a compressible elements also transfer a fixed min block size through the aspect-ratio to become a min inline size (Issue #6341: Compressible elements with aspect ratio)
- Next week the group will come back to Issue #6341 to try and reach a resolution on how to deal with percentage block sizes.
- There were several questions on issue #6488 (After #6320 there’s no way to get an identity transform for interpolation of perspective) and the group ran out of time before consensus could be reached. It will be added to next week’s agenda in order to reach resolution.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: