- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Apr 2020 10:28:04 +0000
- To: public-css-archive@w3.org
> Also noticed that for `<u>H<sub>2</sub>O</u>`, really the right thing is `font-variant-position: sub`, no? Possibly, but that doesn't seem to be very widely supported at the moment. > 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. IMO the spec behavior is the most reasonable result: the line must be uniform across the entire decorated box. If an author expects to have a lot of subscripts, and doesn't like how that interacts with ink-skipping, the two options would be to turn off skipping (so that the underline cuts through the subscripts), or to use `text-underline-position: under` or `text-underline-offset` to move the line lower for all the content. What is categorically wrong, IMO, is for the line to jump up and down on baseline-shifted children of the decorated box. If that result is desired, the decoration should be applied separately to each of the child elements. > what would happen is that they file bugs against Chromium rather than fixing their sites I'm sure that is true, just as they file bugs against Firefox today. But if Chromium (in addition to Firefox) provides clear messaging that "this is the correct behavior, and if your site looks bad, it's on you to fix it" there will be a much stronger incentive than when it's only Firefox trying to hold that line. > Have you contacted to site owners you know look bad with the spec behavior? Yes, at least in some cases; I'm afraid I don't know details of how many such contacts there have been, or how often it has led to a site being fixed. In the case of the BBC site reported in https://bugzilla.mozilla.org/show_bug.cgi?id=1584348, for example, the problem is still present. I suspect that if their site started looking bad in Chrome, however, they'd probably get around to fixing it. Whether you could convince them to fix it before Chrome actually ships a change that "breaks" their site is more questionable, I guess. People love to put things off for another day... -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5002#issuecomment-620520447 using your GitHub account
Received on Tuesday, 28 April 2020 10:28:10 UTC