- From: Raphael via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Sep 2024 08:20:24 +0000
- To: public-css-archive@w3.org
@justinfagnani The most natural way for me: slots would be just a feature of the host element itself and attached to the it in a sort of _new composed tree_, without any shadow boundary. All slotted content would be projected into the _new composed tree_ which would mask the LightDOM of the custom element. Regarding which elements are slottable I cannot think of any restrictions. I know I am lacking a detailed description regarding slots in LightDOM, I just want to express the sentiment that a lot of authors I met during conferences and in my project work (main design system and large component libraries) suffer from the hard encapsulation that ShadowDOM poses onto. This is the main reason. Seeing #10808 empowers this albeit from the CSS side. Either way would be fine for authors I think. -- GitHub Notification of comment by raphaelokon Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10420#issuecomment-2357814286 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 September 2024 08:20:25 UTC