- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Apr 2020 08:47:38 +0000
- To: public-css-archive@w3.org
> if Chrome fixes this behavior, "broken" (not really broken, but visually glitched) sites will suddenly have a greater incentive to correct their content. From my experience in the past, what would happen is that they file bugs against Chromium rather than fixing their sites, and our default choice is to revert the change. Even before that, if regression is known beforehand, our community will not approve shipping the change. It is possible to try to convince the community, but I guess we need more investigations if we want to try that. Two things I can think of: * I agree that Edge's behavior on `<u>H<sub>2</sub>O</u>` isn't optimal, but the spec behavior is not optimal either, looking at the screenshot above, especially with ink skipping on. Are there any other options? * If there were no other options, I think we should try to convince sites to fix before making the change. Have you contacted to site owners you know look bad with the spec behavior? -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5002#issuecomment-620469757 using your GitHub account
Received on Tuesday, 28 April 2020 08:47:40 UTC