- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 May 2025 19:17:40 +0000
- To: public-css-archive@w3.org
> A lot of the problems described above were the problems faced by container queries. It isn't exactly the same, but developers are familiar with the restrictions that CSS containers bring, so it would be good to lean into those patterns. This is somewhat building on how container-queries work, but its fundamentally different. E.g. with this feature its enforcing that you can only respond in one dimension (the height). However the difference is that the height of the iframe _cannot_ be known synchronously. It needs a IPC jump to a different process, hence the issues with loops/hysteresis, etc. -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12229#issuecomment-2905556545 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 May 2025 19:17:41 UTC