- From: Jake Archibald via GitHub <noreply@w3.org>
- Date: Tue, 27 Jan 2026 09:12:01 +0000
- To: public-css-archive@w3.org
I think “we should have these values” is a fair summary of the argument for this feature, but I don't think “no, we should not” is a fair summary of my argument against. I have presented multiple code examples, of things likely to happen in the real world, that show that this feature would be a footgun in practice. I have also shown that this feature hasn't been properly justified. CSS has the ability to pull values from attributes. I haven't seen any reason given why this particular property should have an obfuscated value that does the same thing, while other properties have not. I have not seen any reasoning given of why this feature is worth creating a confusing difference between same and cross-document transitions. The recent discussion doesn't address any of this. Instead, the group acted as if the naming `auto` was the total of the problems here, and that calling it `match-auto` avoids all those problems. It doesn't even address the naming issue. But again, the naming is a small part of the problem here. I want the group to at least try to justify the need for this feature, and that the benefits of it outweigh the footguns it adds to the platform. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12091#issuecomment-3804016788 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 January 2026 09:12:01 UTC