Minutes Telecon 2022-11-16
- There is still discussion necessary on issue #7306 (Move the definition of “display mode” back to Manifest spec) about if this should be generalized before a resolution can be reached.
- Resolved: Take second solution for this case. Update the last remembered size if element doesn’t skip its contents (Issue #7807: content-visibility: auto kinda broken by not using last remembered size with contain: size)
- Issue #3320 (Clarify fragment URLs resolve against the current tree, not document tree) needs more discussion about the motivation behind the behavior before a resolution can be reached.
- Resolved: Add this definition to values-4 and evaluate new definition against existing test suite (Issue #5210: Define when border rounding happens, and to which properties it applies)
- There was disagreement on the value changing fragmentation as proposed in issue #5648 (contain:size shouldn’t fragment as monolithic) as well as how common the use case will be once container queries are more common. Discussion will continue on github.
- Administrative:
- Upcoming meeting updates:
- The group will be meeting next week.
- Next long call is scheduled on Nov 30th.
- plinss gave an update on the server work done to add stability and what is left to do.
Full Meeting Minutes
Minutes Telecon 2022-11-09
- Upcoming meeting updates:
- Next long call is scheduled on Nov 30th.
- Please reply to the email on the private list about if we should cancel the week of 21 November (US Thanksgiving).
- jensimmons and fantasai are organizing a workshop next Monday on Inline Layout.
- Please add feedback and thoughts on the model to collaborate with TAG to the github issue (Issue #7835: Co-authoring CSS Design Principles with the TAG).
- Resolved: Publish css-shapes-1 CRD (Issue #6450: Updated CR of CSS Shapes? Administrative Tracker For external review/publication tracking issues)
- Resolved: Accept proposal (Issue #7956: Behaviour of the finished promise)
- Resolved: view-transition-image-pair [is the property name for the pseudo-element which adds isolation for blending] (Issue #7960: CSS selector keywords)
- Resolved: UA styles on the pseudo-DOM stay in sync with author DOM for any developer observable API (Issue #7812: When to update the pseudo element styles)
- Resolved: Elements under content-visibility:auto element that skip its contents are not eligible to participate in view transition (Issue #7874: content-visibility: auto elements are relevant to the user during a transition)
- Resolved: Change to present tense for ContentVisiblityAutoStateChanged (event and object) (Issue #7603: Incomplete event definition for ContentVisibilityAutoStateChanged)
Full Meeting Minutes
Minutes Telecon 2022-11-02
- The next long-form meeting will be November 30th starting a few hours before the normal meeting time.
- Resolved: We define the first baseline as the highest baseline in all the columns and spanners of the multicol (Issue #7856: First baseline of a multicol)
- Text will be added to Multicol to make sure we define that relpos doesn’t affect baseline alignment
- Resolved: Change the spec to simplify this sizing and figure out what tests we need (Issue #7465: How to properly accommodate margin/border/padding of a subgrid with no item on the edges)
- Resolved: Take the changes listed in this comment (Issue #7612: *-items properties might need to resolve directions early)
- Resolved: Use the writing mode of the parent’s formatting context for staticpos (Issue #7599: align-self / justify-self on abspos elements isn’t back compatible?)
- Resolved: Align justify axis of non staticpos use writing mode of their containing block (Issue #7599)
- The recommendation for issue #3052 (Investigate applying align-content to single-line flex containers) is to close no change based on use counter data from Chromium. Before resolving to close fantasai will verify that accepting the proposal would cause a different to a sample of the sites found in the use counter.
- Resolved: Add a SHOULD requirement for considering the filter effect extent and interaction with UA margin (Issue #7711: filter effects and “relevant to the user”)
- Resolved: Accept the proposed resolutions for items 1, 2, 3, 5, & 6 (Issue #7960: CSS selector keywords)
- Property used on DOM elements to tag them for independent animations: view-transition-name
- The pseudo-element which directly originates from the root element and is the ancestor for all container elements: html::view-transition
- The pseudo-element which animates the size and position for tagged elements: html::view-transition-group(*)
- The pseudo-element which displays snapshot from the old DOM element: html::view-transition-old(*)
- The pseudo-element which displays snapshot from the new DOM element: html::view-transition-new(*)
Full Meeting Minutes
Minutes Extended Telecon 2022-10-26
Publications
View Transitions
- Resolved: Use “snapshot viewport” for root element snapshot and UA CSS to size and position ::page-transition at snapshot viewport (Issue #7859: Define transitions over changing viewport)
- Resolved: ake khushal’s proposal to use pseudo-element syntax for view transitions (Issue #7928: Using pseudo-elements vs shadow DOM syntax)
- Resolved: Go with the Option 3 syntax (Issue #7788: CSS selector syntax for generated elements and API names). [Option 3: we select this as if they are all children of html:html::view-transition, html::view-transition-old(foo), etc]
- Resolved: Name the function .startViewTransition() (Issue #7788)
- Resolved: Synchronously generate styles for pseudo-DOM after DomUpdateCallback and before resolving ready promise (Issue #7812: When to update pseudo-element styles)
- Resolved: Update the UA stylesheet as needed in a new step after the current step 14 of “update the rendering” (after RO callbacks are done) (Issue #7812)
Nesting
- Resolved: Allow relative selectors for both nesting and @scope (Issue #7854: Allow relative selector syntax in @nest rules)
- The group revisited the four proposals to address issue #7834 (Syntax Invites Errors) which are detailed in the spec.
- The original debate was between options 1 and 3 and in the last conversation there was also discussion that option 4 may get better results. Discussion first focused on option 1 vs 3.
- Resolved: We’re taking option 3 over option 1 (Issue #7834)
- It was not clear if option 3 or 4 was better and more examples need to be added as well as further developer engagement around this pair of options.
- Resolved: Change the spec to reflect option 3 (Issue #7834)
- Resolved: Open issue for further discussion of 3 vs 4 (Issue #7834)
Full Meeting Minutes Part I and Part II
Minutes Telecon 2022-10-19
- There will be an extended meeting on Wed Oct 26, 2022 from 7:00am – 10:00am PT
- Resolved: Close no change (Issue #7431: Restrict none/auto/normal from
custom-ident)
- Resolved: Properly define resolution of media type and top-level MQ (Issue #7595: Merge error handling section into evaluating section)
- Resolved: Clarify the spec text to reflect intended unknown mechanics (Issue #7595)
- Resolved: Replace “replace by not all” with “evaluates to false”, open a separate issue on serialization (Issue #7595)
- Resolved: content-visibility applies to elements that can have size containment (Issue #7658: Should content-visibility apply to elements when size containment has no effect?)
- Resolved: For overflow:auto and size containment, 1st phase sizes without scrollbars, 2nd pass adding scrollbars doesn’t change the size (because it is fixed). Clarify (Issue #7875: overflow: auto incompatible with size containment and container queries)
- The discussion for issue #7834 (Syntax Invites Errors) began by reviewing the four proposals and the feedback gathered on them. The voting indicated options 1 & 3 and the group affirmed interest in those options. There was also a desire to investigate option 4 further, but the group ran out of time to discuss further on the call.
Full Meeting Minutes
CSS Values and Units Level 4 WD Updated
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>. We will also be posting a synchronized version of CSS Values and Units Level 3 shortly (as a CR, it needs to pass additional reviews).
Most changes since the last WD are largely error corrections and refinement of existing features, see full changes list. We also added a new section defining in generic terms the computation pattern for coordinating list-valued properties (like background-*), so that it can easily be referenced by other property sets (like animation-*). The remaining open issues are largely centered around two topics: clarifying url() handling and refining details of the viewport units and their interaction with the “initial containing block”.
With the draft in a largely-completed state, this is essentially the last call for wide review. See also the complete list of additions since Level 4.
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 2022-10-12
- There will be an extended meeting on Wed Oct 26, 2022 from 7:00am – 10:00am PT
- Resolved: Incorporate trim-end behavior into the normal keyword (Issue #7055: text-spacing: trim-end is better than allow-end for the normal value)
- Resolved: Add text-justify:ruby, which is like ‘auto’ but disables justification opportunity on spaces and bopomofo (Issue #771: Treatment of multiple Latin words in space-between & space-around)
- Resolved: `rt, rtc { text-justify: ruby; }` to UA stylesheet (Issue #771)
- Resolved: `lang=und` matches :lang(“*”)`, `lang=””` doesn’t match any `:lang()` (Issue #6915: `:lang` for documents without content language and for elements of unknown language; consider `:lang(“”)` over `:not(:lang(“*”))`)
- Resolved: Accept :open and :closed with definitions as proposed by TabAtkins (Issue #7319: Add `:open` or `:top-layer` pseudo class)
- Proposed definitions: The :open pseudo-class represents an element that has both “open” and “closed” states, and which is currently in the “open” state. Exactly what “open” and “closed” mean is host-language specific, but exemplified by elements such as HTML’s
details, select, and dialog elements, all of which can be toggled “open” to display more content (or any content at all, in the case of dialog). Note: Being “open” is a semantic state. An element not currently being displayed (for example, if it is in a display: none container) can still be “open” and will match :open.
- The proposal for issue #7431 (Restrict none/auto/normal from
custom-ident) was to restrict none/auto/normal from custom-ident however, after conversation, there is a desire to revisit in context of the overall custom-ident grammar to ensure this doesn’t make other naming issues worst.
- Resolved: Accept to make & valid everywhere, maps to :scope where not otherwise defined (Issue #7545: Move nest-containing and nest-prefixed selector definitions to Selectors)
- The group is going to think more about the possible use cases around issue #7340 (Allow ‘order’ on table columns) and decide next week if this is something they want to pursue further.
Full Meeting Minutes
Minutes Telecon 2022-10-05
- Resolved: Always ignore transforms on backgrounds of the root element (Issue #6683: Are the rules for interactions of transforms and backgrounds on the root element what we want?)
- Resolved: Always ignore transforms on backgrounds that propagate to canvas (Issue #6683)
- Resolved: Use css-view-transitions as the shortname (Issue #7788: Renaming and brevity)
- There was not consensus on the call the final name the pseudo element currently called view-transitions-images (Issue #7788). Naming it view-transitions-set or view-transitions-group was considered too generic but view-transitions-images was strange because it is a plural and because some folks felt that images evoked a different concept. Just as the timebox ended there was a suggestion of being more verbose in the name since we don’t expect it to be a commonly used property. Discussion on naming will continue on github.
- Resolved: Only consider animations using document timeline for determining when the end of a view transition has come (Issue #7785: Define “active animation” used to signal end of transition)
- Resolved: View animations are still active if there are running or paused view transition animations or any events in the pending event queue associated with animations on these pseudos (Issue #7785)
- Resolved: Rendering suppression uses render blocking to pause update the rendering loop during a view transition (Issue #7784: Define how rendering is suppressed between DOM changes)
- Resolved: Left to left and right to right (Issue #7775: Fallback alignment groups with orthogonal items)
Full Meeting Minutes
Minutes Telecon 2022-09-28
- Resolved: Draft reading-order (minus source value) into css-display-4 ED (Issue #7387: Providing authors with a method of opting into following the visual order, rather than logical order)
- Resolved: Flex baselines take flex ordering into account so first/last use roughly *physical* directions (Issue #7776: Flex container baselines with reverse direction)
- Issue #7774 (Flex container baselines with “flex-wrap: wrap-reverse” present) requires clarifying edits that you should be using writing-mode order.
- Resolved: Last remembered size uses the “stitch together in block axis” bounding box (Issue #7598: Last remembered size when fragmented?)
Full Meeting Minutes
Updated WD of CSS Containment L2
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, as well as content-visibility property, which controls whether or not an element renders its contents at all. This enables heavy optimizations by user agents when used well.
This update publishes about two years worth or refinements, bug fixes, and clarifications, getting closer to stability. A number of open issues remain to be addressed, but the fundamentals are in place. 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-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.)
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: