- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Nov 2020 17:46:12 +0000
- To: public-css-archive@w3.org
Do you have compelling examples for use cases where the specified behavior is better than what Chromium and WebKit happen to do? I'm pretty sure there are some, but examples will help us to distinguish between the two possible courses of action. Some more points: - In terms of minimizing risk to web compatibility, it's pretty clear that changing the spec and Gecko behavior is the safer alternative. - Fixing Chromium & WebKit to match the spec might break libraries that work around this inconsistency (and AIUI are used on a lot of sites) - If there are strong use cases for the specified behavior, we may be forced to introduce a new offset value for web compatibility anyway - I'm guessing that this incompatibility has been around for a very long time? A Chromium bisect shows it has been around since at least M65 -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5659#issuecomment-721280874 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 November 2020 17:46:14 UTC