Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: :host, ::slotted(), ::part() #19

Closed
Westbrook opened this issue Jul 28, 2022 · 4 comments
Closed

Feature: :host, ::slotted(), ::part() #19

Westbrook opened this issue Jul 28, 2022 · 4 comments

Comments

@Westbrook
Copy link

:host, ::slotted(), and ::part() are integral to develop/consuming/understanding styling for elements with Shadow Root. They also have a lot of opportunity to be leveled up with recent advances like :has() and @container. Understanding the current state of their usage and any specific issues that CSS developers might be facing with them would be amazingly beneficial in outlining paths forward with them.

@LeaVerou
Copy link
Collaborator

Great idea!

I think ::part() should be separate than :host and ::slotted() as they are used by different types of developers: the former by web component consumers, and the latter by web component authors, so they are likely to have vastly different exposure stats.

@Westbrook
Copy link
Author

Likely, possibly, hopefully, there's so many known unknowns here, great call!

@LeaVerou LeaVerou added let's do this Accepted suggestion but not in survey yet Feature and removed State of CSS under consideration labels Aug 6, 2022
@LeaVerou LeaVerou moved this to In Progress in State of CSS 2022 Aug 25, 2022
@SachaG SachaG moved this from Let's do this to In survey in State of CSS 2022 Sep 22, 2022
@SachaG SachaG moved this from In survey to Let's do this in State of CSS 2022 Sep 22, 2022
@SachaG
Copy link
Member

SachaG commented Sep 26, 2022

I ended up deciding to have them all in the same question, in the interest of keeping the survey length manageable.

@LeaVerou
Copy link
Collaborator

LeaVerou commented Oct 3, 2022

Last moment thing: if we can only have one question about this, let's just keep ::part() and drop the others. Now that they're together, it's hard to gauge how many developers are aware of ::part(), and it's far more useful to know whether developers use that / know about that than the other ones that are only used in component implementation. If we have a question about ::part() we can add the other next year, but if we have them together, we can never separate them without losing historical comparison.

@LeaVerou LeaVerou moved this from Let's do this to In survey in State of CSS 2022 Oct 3, 2022
@LeaVerou LeaVerou added in survey and removed let's do this Accepted suggestion but not in survey yet labels Oct 3, 2022
@SachaG SachaG closed this as completed Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In survey
Development

No branches or pull requests

3 participants