- From: Westbrook Johnson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 09 Apr 2024 21:30:54 +0000
- To: public-css-archive@w3.org
@trusktr the parallels between your use case and being able to accept native elements into slots like `<details>`, `<dt>`, `<ol>`, `<table>`, `<ul>` run quite high. It makes me wonder at which point we could request/expect actual numbers on the cost of this sort of selecting from Implementors and not just allegorical numbers see on the initial v0 implementations in 2012. While the underlying technique between this and `@scope` are likely different, it would seem that they should embody similar issues in this area. Is that API targeted to be bound by the same restrictions? What can be learned from that which may allow us to make preciously enforceable advances in this area? I’d go so far as to volunteer time to investigate this more deeply if I could find some one versed in showing me a baseline as to how to get started working with one of the engines and a baseline of the associated selector hashing from which to work. I’d love this to be the next container queries, some thing we could never do… until we did! -- GitHub Notification of comment by Westbrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7922#issuecomment-2046083482 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 April 2024 21:30:55 UTC