- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Jan 2024 00:03:49 +0000
- To: public-css-archive@w3.org
> Given that this never worked so far, there shouldn't be any backwards compat issues. Unfortunately, we can't rely on that. Unlike in JS, where doing something wrong like this would have *raised an error* and probably force you to fix your script, in CSS all this means is that your property will fail to transition. And people sometimes write this sort of incorrect code, and then just *leave it in their stylesheets*, since it doesn't do anything. So there's always a compat risk when we make some "reasonable, but wrong" behavior suddenly become correct, and suddenly changes the behavior of the page. (At the time the property was written, the author probably intended it to transition, but now that it hasn't, they might have continued with further work that assumes the transition doesn't happen, and would do something wrong if it suddenly started transitioning.) (It's usually fine to make stuff that's more *obviously* invalid become correct, so stuff like adding entirely new properties is virtually always fine to do. We have an advantage over JS in this regard, where they regularly run into compat adding new methods to existing objects.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1899410119 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 January 2024 00:03:51 UTC