- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Jul 2024 17:54:16 +0000
- To: public-css-archive@w3.org
I just responded about the `all` option in https://github.com/w3c/csswg-drafts/issues/626#issuecomment-2233864834 ; I don't think that would be sufficient. I think as far as browser engine developers go, I think I lean towards being willing to try to make changes that might cause small amounts of broken content. However, I think this is *way* past where I'm willing to go in terms of breaking content, because given the number of problems I saw on top site homepages I suspect there's going to be a large number of sites broken in various ways through the long tail of web content. I think the CSS WG has had extended discussions of compatibility problems whose effects were at least a hundred times smaller than this. I also think parts of a page moving around that the author didn't intend to animate can substantively affect usability and accessibility, and is more significant than "doesn't break actual readability". -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10576#issuecomment-2233887787 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:54:17 UTC