On Fri, Feb 24, 2023 at 5:49 AM Yoav Weiss <yoavwe...@chromium.org> wrote:
> On Fri, Feb 24, 2023 at 11:27 AM Manuel Rego Casasnovas <r...@igalia.com> > wrote: > >> There's a CSSWG issue about this topic in particular: >> https://github.com/w3c/csswg-drafts/issues/7441 > > > Is this something that can be put on the agenda for the CSSWG to discuss? > I added this to the group's (long) agenda backlog. (Also, a few other relevant CSSWG issues I found were w3c/csswg-drafts#1888 <https://github.com/w3c/csswg-drafts/issues/1888>, w3c/csswg-drafts#2796 <https://github.com/w3c/csswg-drafts/issues/2796>, w3c/csswg-drafts#5225 <https://github.com/w3c/csswg-drafts/issues/5225>, w3c/csswg-drafts#5518 <https://github.com/w3c/csswg-drafts/issues/5518>, and also some minutes from July 2020 <https://lists.w3.org/Archives/Public/www-style/2020Aug/0006.html#:~:text=vertical%2Dalign%3A%20super%20and%20font%20metrics> and from September 2020 <https://lists.w3.org/Archives/Public/www-style/2020Sep/0023.html#:~:text=should%20we%20add%20the%20super%20and%20subscript> .) One other point that I missed yesterday is that one of the key reasons that these new properties can't be used for the default rendering of <sup>/<sub> elements is that they don't support *nested* subscript/superscript. One of the goals of the 2011 discussion I cited above was to solve that issue in a reasonable way. All of the current ways of doing typographically correct super/subscripts only support a single level of super/subscript, and not nesting. This works for the majority of use cases, but not all. -David -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAG0MU3ht%3DrZwCtQoUWJXR4avCaY2TvAa9NMiYAfMsdan94wzVw%40mail.gmail.com.
