- From: Simon Pieters via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Apr 2022 12:32:43 +0000
- To: public-css-archive@w3.org
> If it doesn't matter too much, then having interop or not doesn't matter either. I disagree, getting interop on the details even if the details are by themselves not important makes for a robust and predictable platform where developers can test what happens in one UA and expect it to work the same in others. Specifying something that no UA implements now means the first to conform will make interop worse and risk breaking some web content. I object to this. Ways to resolve my objection: - get sign-off from relevant folks from at least two of Gecko, WebKit and Chromium that they want to change to conform to the spec. In this case, they should all have bugs filed to track the issue. - specify what WebKit and Chromium do. In this case, we should file a bug for Gecko. -- GitHub Notification of comment by zcorpan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6542#issuecomment-1110945305 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 April 2022 12:32:45 UTC