- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Sat, 29 Aug 2020 17:43:39 +0000
- To: public-css-archive@w3.org
> I don’t agree with the flip. There are plenty of places where we choose a value/formula/algorithm to use, and only _very_ reluctantly agree to variations because there _are_ places where we are concerned it would break web content. From a browser developer’s point of view, the flip is relevant. The CSSWG is proposing that browsers make a behavior change, and for what? Will it be a progression? I agree it would cause browsers to match each other more closely, but you have to remember that way more users use the same browser over time (multiple releases) than who use multiple browsers at the same time. And from an author’s point of view, they just asked “please make this text sup.” They didn’t specify an exact pixel offset. If superscript positions are 1px different in some browsers, does that break their content? Seems unlikely. So from a user’s point of view, the risks outweigh the benefits, and from an author’s point of view, they probably don’t care about this specific 1px difference in these specific formulas. I don’t agree that standardizing things just for standardization’s sake is the right thing to do in every case. > I don't see a huge issue on everyone aligning on 1em/3+1px, 1em/5+1px instead of 1em/3, 1em/5. This would be a reasonable path forward. I can try to dig up the rationale for the +1px. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5225#issuecomment-683321234 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 29 August 2020 17:43:40 UTC