- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Apr 2023 09:54:15 +0000
- To: public-css-archive@w3.org
This may be a bit too much magic going on I think. Some things that come to mind: - With automatic detection, this could mean that a perfectly working scroll-driven animation suddenly stops working due to some margin bleeding out of an element down in the tree as it causes the scroller to scroll on the other axis as well. - I guess this would require an extra layout pass to determine which axis is overflowing? - Looking at specs like scroll snapping, the axis in `scroll-snap-type` is mandatory instead of being auto-derived from overflow _(which it could, right?)_. For consistency, best to keep things similar. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8745#issuecomment-1521506642 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 April 2023 09:54:16 UTC