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
Minutes Telecon 2021-07-21
- Resolved: Republish CSS Fonts L4 and Fonts L5 (Issue #6462)
- Resolved: Republish CSSOM (Issue #6446)
- Resolved: Highlights associated with creator document. Throw on mismatches when registering ranges/etc. (Issue #6417: Specifying behavior for Highlights involving multiple documents)
- Resolved: UA does not add any default styles to custom highlights (Issue #6375: Need clarification on expected default values for style properties)
- Resolved: Move order property to Display module (Issue #5865: Order property definition only mentions “flex items”)
- Resolved: Close no change, Firefox is correct (Issue #4852: Indefiniteness when sizing grid tracks in a flexible flex item)
- Discussion will continue on github for issue #4311 (Should a definite flex-basis always make the main size be definite?) to determine if the proposed behavior is followed by all browsers or if Firefox is doing something different.
- Resolved: Defer [scrollbar-color accepting a single color] to L2 (Issue #5651: Using scrollbar-color to tint the scrollbar)
- The group began to discuss issue #2252 (Is it possible to have a position: sticky horizontal scrollbar?) and came to a common understanding of the problem. However, there wasn’t time to discuss possible solutions so the topic will continue on github.
Full Meeting Minutes
New Viewport Units Introduced to Values and Units L4
The CSS Working Group has published an updated Working Draft of CSS Values and Units Level 4. This specification defines the CSS property definition grammar, and the value types that are common across many specs, such as <length> or <string>.
New to this draft are the large, small, and dynamic viewport units (lv*, sv*, dv*) which allow authors to more precisely size things in relation to the dynamically retracting UI of mobile Web browsers. See discussion. Other significant changes since the last Working Draft are all 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-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.)
Minutes Telecon 2021-07-14
- Resolved: Update WD of css-color-5
- Resolved: Publish updated CR of css-counter-styles-3
- Resolved: If a layer is introduced in a non-global conditional rule (such as a container query), it always affects the layer order, whether or not that query matches (Issue #6407: Do conditional rules impact layer order?)
- Resolved: “dynamic” viewport does indeed use units, not env() (Issue #4329: Add vhc value and issue #6113: Add lvh+lvw values)
- Resolved: Add lvh as explicit “large viewport” unit (Issues #4329 and #6113)
- Resolved: vh/etc are deliberately UA-defined (Issues #4329 and #6113)
- Resolved: New WD of Values 4, after viewport units edits have been made
- Resolved: Elements with a zero-area border-box do not directly contribute to scrollable overflow area. (Issue #4791: Scrollable Overflow contributions of zero height/width elements)
- Resolved: Close issue, one color accent-color for now (Issue #6159: accent-color background colors and contrast)
- Resolved: Rename to ‘both-edges’ (Issue #6349: Rename scrollbar-gutter:both)
- Resolved: Close WONTFIX; scrollbar-width remains non-inherited (Issue #4799: scrollbar-width should be inherited)
- Resolved: Drop the light/dark keywords from scrollbar-color (Issue #6438: Remove light and dark keywords of scrollbar-color in favor of color-scheme)
Full Meeting Minutes
Minutes Telecon 2021-06-30
- Resolved: Add custom properties support to pseudo elements (Issue #6264: Highlight pseudos and custom props)
- Resolved: Layer rules respect conditionals, and are ignored in non-global conditionals (Issue #6407: Do conditional rules impact layer order?)
- Resolved: Name-defining at-rules follow layer order for collision resolution, similar to specificity resolution (Issue #6404: What happens to name-defining @-rules nested inside @layer?)
- Review is requested for the proposed text on issue #6113 (Add lvh+lvw values) before a resolution is requested next week.
- Resolved: The issue is resolved [now that we have size-adjust] (Issue #5533: Reduce layout shift via @font-face descriptor(s) overriding inline spacing)
- Resolved: Drop color-adjust(), stick with relative color syntax for color manipulation for now (Issue #6179: Is color-adjust() needed, now that we have relative color syntax?)
- Please add feedback to issue #6399 (Remove the :scope dependency from the relative selectors definition) to help determine which of the proposed solutions to take.
Full Meeting Minutes
Minutes Telecon 2021-06-23
- Resolved: css-fonts-5 to FPWD
- Resolved: Add leaverou as co-editor css-color-4
- The editors of Contain 3 will add a bit more detail to the 1D containment section and then request FPWD; hopefully next week.
- Resolved: Update spec to acknowledge effects of filters. No other change. (Issue #6325: paint containment vs filter effects)
- Resolved: Degenerate aspect ratios derived from SVG width/height attributes fall back to viewbox aspect ratio (whether due to negative values or zero values) (Issue #6286: SVG degenerate aspect ratios)
- Resolved: Accept proposal for continuous distribution of space to intrinsic grid tracks (Issue #6078: Distribution of intrinsic sizes according to flex factors doesn’t handle sum < 1)
- Resolved: Alignment via auto margins disables content baseline-alignment the same way as align-self values with the same effect (Issue #5923: baseline-alignment and auto margins)
- Issue #5896 (overflow-clip-margin + border-radius continuity adjustment) needs spec text and/or images added to better understand the examples.
Full Meeting Minutes
Minutes Telecon 2021-06-16
- Resolved: Add new keyword to forced-color-adjust as described above, apply it in UA default stylesheet for SVG root element (Issue #6310: Spec currently breaks use of currentColor for SVG icons in WHCM)
- The group generally felt that ‘size-adjust’ could be shipped soon (Issue #6371: Is the ‘size-adjust’ descriptor stable enough to ship?) however they wanted to first get feedback from myles and publish the FPWD for Fonts 5. The goal is to have a draft ready in about a month.
- Resolved: Switch ic and ch to ic-width/ic-height/ch-width (Issue #6288: Clarify/reconsider interaction of new font-size-adjust options with writing modes)
- Resolved: Add style containment back to ‘strict’ and ‘content’ values of ‘contain’ (Issue #6287: ‘contain: stricter’ like strict + style)
- Resolved: Incorporate visualViewport into cssom-view and add bokand as editor (Issue #6339: Merge visualViewport into working group)
- Resolved: Clamp to 1px for both getComputedStyle() and interpolation as well (Issue #6320: clamping of perspective() function to >= 1px should affect interpolation | Issue #6346: clamping of perspective() function should affect resolved value of transform)
- Resolved: Accept edits (Issue #5985: Clarify whether collapsed flex items influence the flex container’s intrinsic main size)
- There is some clarification needed for issue #4791 (Scrollable Overflow contributions of zero height/width elements) however the group ran out of time on the call to go into much detail.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: