- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Nov 2024 11:19:06 +0000
- To: public-css-archive@w3.org
> @jakearchibald It's not good to fixate on complex websites with complex underlying infrastructure I don't think I am. My point is that `auto` will behave confusingly different on MPA vs SPA. The complexity is hidden behind the word `auto`. > In CSS we try to make it easy to do the obvious thing I agree with this, which is exactly why I'm arguing against the behaviour of `auto` here. It's in no way obvious. It'll work in SPA and be kinda faulty in difficult-to-figure-out ways on MPA. The separate features of `attr(id ident)` and `match-element` don't have this issue. One works the same on MPA and SPA, and another doesn't work on MPA. It avoids the "kinda works, but doesn't in weird ways" issue that `auto` gives us. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10995#issuecomment-2452957918 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 2 November 2024 11:19:07 UTC