CSS WG Blog – Minutes Toronto F2F 2019-06-04 Part I: Selectors 3; Upcoming F2F; Publish Early, Publish Often; Tables 3

This is a page from the Cascading Style Sheets Working Group Blog. Some other places to find information are the “current work” page, the www-style mailing list, the Future of CSS syndicator, and the issue list on Github.

Do you want to know how the CSS WG works? Fantasai has written about:csswg, An Inside View of the CSS Working Group at W3C.

Minutes Toronto F2F 2019-06-04 Part I: Selectors 3; Upcoming F2F; Publish Early, Publish Often; Tables 3

By Dael Jackson July 6, 2019 (Permalink)
Categories: resolutions

Selectors 3

Resolved: Draft :muted, :seeking, and :stalled pseudos. (Issue #3821: Additional resource state pseudo-classes for media elements)
- The definitions of exactly when these apply needs work.
- There was a desire to also have the ability to style for a buffering state, but there was no clear HTML property to hook into for that case.
Resolved: Add :volume-locked. (Issue #3933: “effective media volume is mutable” pseudo-class for media elements)
- There was some further discussion of merging :volume-locked and :muted into a functional :volume pseudo-class.
There is still feedback that implementing :has will not be easy or performant. There was some suggestion of breaking off a more limited section like has-child but that causes concern that it’ll lead to 50 different pseudos to do everything scoped into :has
The issue to allow for styling of password reveal via a pseudo-element and pseudo-class (Issue #3934) generated a lot of discussion around usage. The class matches the control as a whole when the password is revealed and the element matches the icon to click in order to see the password.
- The use case for the element is to allow the show password icon to be consistent with branding, however that raised concerns that it would train users to put passwords in any type of yield instead of only password ones.
- There was an additional use case to detect if a browser will already insert the symbol.
- There are other use cases beyond passwords that are by default hidden and may want a show option, such as CVV fields. One argument was that these should be considered password fields.
- This proposal needs to be considered in conjunction with the previous resolutions for input-security to come up with one consistent approach, even if it means changing the original input-security resolution from last year.
- This proposal also needs to be considered in conjunction with other use cases for widgets and icons inside the input field, e.g. for clearing the input or annotating validation state.

Full Minutes || Spec Referenced

Upcoming F2F

Resolved: Jan 22-24 for A Coruña meeting, pending final approval from Igalia.
Apple has offered to host the Spring 2020 meeting

Full Minutes

Publish Early, Publish Often

Resolved: Allow editors to publish at-will, under the discussed caveats. (Caveats: This can only be done when the only changes are non-normative/editorial and non-controversial OR the group already approved the exact wording. This only applies to WDs, not anything higher in the REC track. When this occurs the author must include it in the changes section with a link to the diff and send an email to www-style about the publication.)

Full Minutes