Minutes Telecon 2022-06-29
- Reminder to put on the wiki if you’re attending the August F2F, especially if planning to be in person
- Resolved: Publish new WD of Images 4 (Issue #7043: Long overdue for republishing)
- Resolved: Change initial value of ‘container-type’ to “normal” (Issue #7402: Rename container-type: none to normal)
- A new issue will be opened to discuss if there should be a blanket restriction none/normal/auto in custom idents
- Resolved: Rename to checkVisibility() (Issue #7317: Rename Element.isVisible to Element.isHidden?)
- Oriol will add specific cases to consider on issue #7103 (The shape of box-shadow should be a circle for a box with border-radius:50% and big spread) and then the group will take up the conversation at the F2F where there’s more time to spend.
- Resolved: Start new draft of variables-2 and add custom units as described here (Issue #7379: Custom units as simple variable desugaring)
- masonf will discuss with the OpenUI group if the proposal in issue #7319 (Add `:top-layer` pseudo class) should be a pseudo-class or pseudo-element.
Full Meeting Minutes
Minutes Telecon 2022-06-22
- Resolved: CSSWG F2F in NYC Aug 1-3, further details incoming on private list
- Please RSVP on the wiki as soon as possible if planning on attending in person or virtually in order to get logistics confirmed
- Resolved: Republish Color 4 and 5 (Issue #7393: CSS Color 4 to Candidate Recommendation)
- Resolved: Color 4 to CR when timing permits (Issue #7393)
- A resolution for republishing will be called next week so that people have time to review the changes (Issue #7043: Long overdue for republishing)
- Resolved: Initial value is `none` (Issue #7066: Revisit decision to make style the default container type)
- Resolved: All elements are style containers by default (Issue #7066)
- Resolved: Go with Delan’s option 2 [For ::highlight pseudos, we redefine the “inherited value” of ‘color’ at the root, so instead of being the initial value (as normal) it is currentColor]. (Issue #6774: Defaulting ‘color’ in :root highlights)
- Resolved: Fullscreen elements should inert the stuff behind them, and match :modal (Issue #7311: Should :fullscreen be a modal state?)
Full Meeting Minutes
Minutes Telecon 2022-06-15
- There were several images added to issue #7251 (Composition of Inset Shadows), but none of them were an exact match for fantasai’s proposal. More images will be added and discussion will continue on GitHub
- Resolved: Move color-contrast() to CSS Color Level 6 (Issue #7310: Is color-contrast() ready to ship?)
- Resolved: color-mix() and gradient non-sRGB interpolation are “ready to ship”, add to Snapshot 2022 (Issue #7310)
- Resolved: color-mix() returns color() for sRGB mixes (Issue #6206: Clarify serialization of color-mix())
- Resolved: Specified style maintains calculations, computed style computes everything as far as possible (but maintains currentColor’s identity), resolved color resolves through to absolute color (Issue #6168: What should the behavior of the CSS Color 5 color functions be when passed ‘currentcolor’ as ‘color’)
Full Meeting Minutes
Minutes Telecon 2022-06-08
- The polls run on twitter for the name change in issue #7317 (Rename Element.isVisible to Element.isHidden?) produced reasons against both names. checkVisibility was also suggested and had mixed support. Bikeshedding will continue on github to collect ideas.
- The concerns about a previous resolution explained in issue #7066 (Revisit decision to make ‘style’ the default ‘container-type’) were around both author clarity and performance issues in some cases. Most of the group’s focus was on ensuring that the property works well for the authors. There was a new proposal to use longhands that needs to be discussed more as a potential solution before the group tries to reach a resolution.
- Resolved: Keep ‘distribute’ keyword alias (Issue #7322: Consider removing distribute value for text-justify from the spec)
- Resolved: text-align: match-parent computes to ‘start’ on the root element (Issue #6542: text-align: match-parent on the root element with direction: rtl doesn’t match browsers)
Full Meeting Minutes
Minutes Telecon 2022-05-25
- Future meeting timing:
- The deadline for TPAC meeting requests is the end of May. Please send any preferences for meeting days to the private list.
- Next week there will be an extended meeting to cover the Selectors topics.
- There have been some suggestions to have a hybrid in person/remote session over the summer. If there is interest please reach out to the private list.
- iank introduced the concept of CSS Anchor Positioning to allow positioning elements relative to other elements in the DOM. There were some initial questions and positive feedback. Discussion will continue on the private github until the proposal is formally moved into the working group’s scope. Any substantial changes will also be noted in github issue #7282 (Introduce CSS Anchor Positioning).
- More examples will be added of the current unexpected behavior mentioned in issue #7251 (Composition of inset shadows). astearns will also do research into if there is already examples we can follow in the Adobe products.
- Resolved: Leave text-shadow spread details undefined right now, with possibility of specification later after impl experience (Issue #7250: Text shadow spread corners)
- Resolved: No change (Issue #7249: Make U+0000 invisible?)
- Bugs will be filed with the browsers to see if they are willing to align to the spec on issue #6542 (text-align: match-parent on the root element with direction: rtl doesn’t match browsers). If the browsers have specific reasons to not conform to the spec the group will consider changing the spec.
- The features listed in issue #7310 (Are these features ready to ship?) are not ready to ship yet, but there is interest in prioritizing them to become ready to ship.
Full Meeting Minutes
Minutes Telecon 2022-05-18
- Resolved: Remove checkInert from IsVisibleOptions (Issue #7274: isVisible inert option)
- There were some concerns about the proposed new keyword for font-display (Issue #7271: Add a font-display keyword to eliminate @font-face FOIT & layout shifts) encouraging authors toward behavior that is bad for users. Discussion will go back to github to discuss further the intent to assist authors in making a decision they’re already trying to make and how to balance that against the concerns.
- Resolved: forced-color-adjust doesn’t do anything on highlight pseudos, and highlight pseudos take their forced color state from the originating element (Issue #7264: Highlight pseudos and forced-color-adjust)
- Resolved: Issue of topmost modal dialog to be addressed with a pseudo-class (name TBD) (Issue #7258: Should :active apply to dialogs?)
- Resolved: Add :-webkit-autofill in an appendix of selectors 4 (Issue #7257: List of -webkit- legacy aliases)
Full Meeting Minutes
Minutes Telecon 2022-05-11
- Resolved: thin, medium, and thick will be defined as 1px, 3px, and 5px respectively. (Issue #7254: Specify exact pixel values for border-width: thin, medium, thick)
- More research needs to be done on current behavior and complexity to change implementations prior to reaching a decision on issue 7164 (How to handle linked list-valued properties?)
- Resolved: Always require inline-end padding to be added against the inline-end alignment edge for block/flow layout when it’s a scroll container, thus matching the tests. (Issue #129: Clarify padding in overflow content)
- Resolved: Accept the proposed PR. (Issue #7101: Highlight pseudos and emphasis/underline properties)
- More testing is required around filter and backdrop-filter to determine a resolution for issue #455 (backdrop-filter and visibility)
- The Safari and Blink teams need to investigate the web compat of solving issue #7227 (counter-reset in UA sheet causing some compat issues) without magic
Full Meeting Minutes
Updated WD of Selectors Level 4
The CSS Working Group has published an updated Working Draft of Selectors Level 4. Selectors are patterns that match against elements in a tree, and are used most famously in CSS style rules as well as various Web platform APIs.
This long overdue update adds quite a few new pseudo-classes: :defined, :modal, :fullscreen, :picture-in-picture, :muted, :volume-locked, :seeking, :buffering, :stalled, :autofill, and :user-valid. It also adjusts parsing rules for most pseudo-classes such as :is() that accept selectors (but not :not()) to ignore invalid selectors in their arguments, preventing these from invalidating the entire selector. 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 ([selectors-4]) and your comment topic in the subject line. (Alternatively, you can email one of the editors and ask them to forward your comment.)
CSS Text Decoration L4 Update
The CSS Working Group has published an updated Working Draft of CSS Text Decoration Level 4. This module contains the features of CSS relating to text decoration, such as underlines, text shadows, and emphasis marks.
Updates in this draft include:
- Adding spread distance to
text-shadow
- Adding
inset to text-shadow
- Clarifying application of
text-decoration-skip-ink
Further planned work on this module includes:
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-text-decor-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-04-27
- Resolved: Republish Will Change 1 as CRD (Issue #7177: Republish)
- Resolved: Add CanvasFilter to PaintRenderingContext2D (Houdini Issue #1056: Add CanvasFilters to PaintRenderingContext2D)
- Resolved: Remove
1d-image from image for now, open a separate issue to discuss it (Issue #2532: Issues with listifying border-color)
- Resolved: NaN escaping calc() tree is coerced to zero (Issue #7067: Make top-level NaN be invalid at computed value time instead of ∞)
- There was discussion around what would be referenced by the proposed :modal pseudo-class (Issue #6965: Add :modal-dialog pseudo-class). If it’s things appearing on the top of the page, :top-layer may be a more appropriate name. Concern was expressed about if the :modal name was going to be too broad for an initial pseudo-class and if the property should start specific and then create a generic as more use cases develop. Alternatively, a broader name would allow clearer combination with other pseudo-classes and future extension without creating a lot of pseudo-classes. Discussion will continue on github and the group will continue to engage with the OpenUI group on this topic.
Full Meeting Minutes
![[Photo: group photo of the CSS working group in San Francisco]](/Style/CSS/csswg-2016.jpg)
Contact: