- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Sat, 02 Nov 2024 00:54:56 +0000
- To: public-css-archive@w3.org
@jakearchibald It's not good to fixate on complex websites with complex underlying infrastructure. Sure, there a many websites that use a framework that can enable SPA or MPA rendering, and will switch between them. But there are also many smaller sites that are not so complicated, designers who are working in much simpler environments, and we want CSS to be designed to be simple and easy for them to use, too. In CSS we try to make it easy to do the obvious thing. If I gave you (a human, not a computer system) a DOM tree and a change function, and said, "do the obvious thing to match the elements across the changes I made", then using whichever of element identity or element ID was available to me would be pretty reasonable, right? If you want to do something specific, there's syntax to do that specific thing. If that syntax feels awkward, we can improve it. But purpose of an `auto` keyword is to make the obvious thing easy to request, and have the UA figure it out. And that's what it's doing here. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10995#issuecomment-2452772866 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 00:54:57 UTC