W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2020

Re: [csswg-drafts] Interoperable font metrics (#4792)

From: jfkthame via GitHub <sysbot+gh@w3.org>
Date: Wed, 26 Feb 2020 21:46:46 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-591660921-1582753605-sysbot+gh@w3.org>
> > The final piece would be to add a from-font value to each of these properties (distinct from auto), and define exactly what it means in terms of metrics from an OpenType font file
> I believe this fails the “browsers having to parse font files” test.

Yes - I figured you probably wouldn't be keen on this value (though we have `from-font` for a couple of the text-decoration properties; doesn't that require browsers to parse font files, too?) Anyhow, I see it as an optional part of the overall suggestion; I think it'd be logical to include a `from-font` value, but it's not required in order for the properties to be useful.

> Just to make sure I understand, would these properties apply to the block container? Non-inherited? And would they override any/all ascent and descent values for every inline descendent?

I haven't really thought about how inheritance etc ought to work... the suggestion that an author might write

    :root { font-ascent: 80%; font-descent: 20%; font-linegap: 10%; }

was based on the idea that these properties would inherit (as percentages, to be resolved for each element against its used `font-size`), but maybe that's not the right approach.

Just throwing ideas out, really, and happy to hear ideas on how it would best work (or why it wouldn't).

GitHub Notification of comment by jfkthame
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4792#issuecomment-591660921 using your GitHub account
Received on Wednesday, 26 February 2020 21:46:48 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:01 UTC