- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jul 2024 16:56:18 +0000
- To: public-css-archive@w3.org
> @nt1m `size-interpolation` was one of the two proposals I used to _start_ the discussion of bikeshedding the name -- so I would have been fine with it (particularly if it were the original decision rather than a later revisit), but the discussion at the face-to-face (minutes at [#10294 (comment)](https://github.com/w3c/csswg-drafts/issues/10294#issuecomment-2165268969)) moved away from that suggestion. > > @LeaVerou I don't want to combine it with something that people actually want to change, because this is designed to be a compatibility opt-in for something that we'd prefer to make the default but can't because of compatibility. It's something you should be able to set once on the root to opt in to the "correct" behavior and then never touch again. If we combine it with something else then people need to remember to re-state that opt-in at each use. See the minutes in [#10294 (comment)](https://github.com/w3c/csswg-drafts/issues/10294#issuecomment-2165268969) (and some of the prior comments) for some discussion of this. To re-iterate the feedback we gave in [this feature’s TAG review](https://github.com/w3ctag/design-reviews/issues/955#issuecomment-2121492620), given that the result of the change is a slight glitch that doesn’t break actual readability, I think we should reconsider simply making the change rather than introducing these awkward opt-ins, or at least digging more into the data to get a fuller picture of the compat implications. We should not be introducing warts into the language simply to avoid examining the compat implications fully or just to be conservative, but when the impact of the wart on authors is *genuinely* smaller than the impact of the compat implications. Or perhaps we can introduce certain restrictions that serve use cases while minimizing breakage. E.g. I wonder if it would be more web-compatible to only transition between these values when a `width`/`height` transition is explicitly requested, rather than when implicitly included via `all` (either explicit or omitted). -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10576#issuecomment-2233767474 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 July 2024 16:56:19 UTC