- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jul 2024 17:45:52 +0000
- To: public-css-archive@w3.org
> 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). So looking at the sites that were problematic at the time (today there would likely be new sites showing up as problematic in addition to old ones dropping off the list): * stackoverflow.com (at the time, got it from https://web.archive.org/) was using `transition-property: width, height`. Today the site has been redesigned and no longer has the part that had the problem. * https://www.alibabacloud.com/en uses `transition-property: height` * intuit.com today it uses `transition-property: padding` which wouldn't have triggered the problem in the first place. I can't get an appropriately-aged site in https://web.archive.org/ to load. * cricbuzz.com and ups.com (today) do use `transition-property: all` So I don't think that helps sufficiently. (Remember also that this is from a sample of loading homepages without any user interaction, which in general doesn't trigger that much animation compared to the animation that results from user interactions.) -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-2233864834 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 17:45:53 UTC