W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2020

Re: [csswg-drafts] [css-scoping] Consider aligning ::slotted() for fallback content with implementations (#5482)

From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
Date: Wed, 02 Sep 2020 00:13:27 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-685200021-1599005606-sysbot+gh@w3.org>
Thanks @lilles much appreciated. So comparing `::slotted()` with something like `focus-visible` which is relatively new:

`focus-visible` 2.18%
<img width="645" alt="Screen Shot 2020-09-01 at 5 05 56 PM" src="https://user-images.githubusercontent.com/865244/91917697-84b4ed80-ec75-11ea-907e-3aa4fda5cc84.png">

`::slotted()` .19%
<img width="646" alt="Screen Shot 2020-09-01 at 5 07 28 PM" src="https://user-images.githubusercontent.com/865244/91917749-ae6e1480-ec75-11ea-964d-301b6d81d1f7.png">

While `::slotted()` is used, as @lilles  noted, this doesn't account for if it is default content or not and my hunch is that most don't target default content. I think, if feasible, is for Chrome (since they have a patch ready) to ship to canary and dev and see if bug reports come in from the change. If we don't, then potential compat concerns will continue to rise.

I'd love to see us at the very least try and determine if the compat risk is large, which currently being well under 1%, while not inconsequential I do think we're at a point this is a worthwhile change. If we don't then we'll need to add some type of switch to allow for default content to achieve the behavior as currently specified.

GitHub Notification of comment by gregwhitworth
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5482#issuecomment-685200021 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 September 2020 00:13:29 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:15 UTC