- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 May 2020 22:20:50 +0000
- To: public-css-archive@w3.org
I don't see why `safe center` is generally a better fallback behavior. If it creates unscrollable overflow then sure, but that's what the magic "no value" is for, right? UAs should just implement that instead IMO. Also, it sucks to retroactively change interoperable features that's already been shipped for years by multiple UAs. We should try to avoid that unless it's obvious the feature has major issues when used in practice. I don't see any evidence of that here. For these reasons I'm opposed to this change. FWIW, it seems like a design error to me that the overflow behavior is built-in without giving authors any way to override it. There used to be a way to specify a fallback behavior explicitly (which Gecko implemented and then had to remove :disappointed:). I think we should re-introduce that feature (#1002). We're just waiting on the CSSWG to come up with a syntax there... We can ship that fairly quickly once we have the syntax. -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5088#issuecomment-634311422 using your GitHub account
Received on Tuesday, 26 May 2020 22:20:55 UTC