- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Apr 2020 08:54:05 +0000
- To: public-css-archive@w3.org
I don't think the Edge behavior is desirable here. It would mean that rendering of underlines will be broken in the presence of subscripts: `<u>H<sub>2</sub>O</u>` will forever look bad. The inconsistency between behavior when the child box is moved down vs when it is moved up also seems bad. (What about the case of overlines? Would the opposite apply there?) IMO the spec should be kept as is, because this is the better behavior; it gives authors simple, consistent behavior, and makes it easy to get the result that is usually "right". With the proposed change here, it would become extremely difficult for an author to produce the effect of a continuous underline on text that includes subscripts. I'm aware there are sites that would exhibit a "regression", but the nature of the regression is that it's a visual glitch rather than something that seriously impacts functionality, and it's easily fixed by correcting the text-decoration styling. It's currently difficult to persuade site authors to care about fixing it because the dominant browser doesn't follow the spec, but if Chrome fixes this behavior, "broken" (not really broken, but visually glitched) sites will suddenly have a greater incentive to correct their content. -- GitHub Notification of comment by jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5002#issuecomment-618890409 using your GitHub account
Received on Friday, 24 April 2020 08:54:07 UTC