- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Aug 2022 15:01:08 +0000
- To: public-css-archive@w3.org
I think the summary was: * most of the people present were leaning towards leaving the spec as-is (saying that `ch` units do cause font downloads). However, given that @litherum , who raised this issue, was not present, we decided to defer trying to resolve the issue for 2 weeks. (Otherwise we probably would have resolved.) * I think there was consensus that, whether or not `ch` units trigger font download, if the font *is* downloaded, then `ch` units get re-resolved if the newly-downloaded font is an earlier font. (This, in turn, means that the implementation complexity of triggering downloads is merely the triggering of downloads.) * We considered and rejected the possibility of using .notdef glyphs rather than 0 glyphs. * There was another possibility (option (2)) that I think was also rejected, though I can't actually remember from the notes what it was, and I don't think we discussed it much. * The main discussion was between what is listed as option (1) (leave the spec as-is) and option (3) (don't trigger font downloads for `ch`/`ex`/`ic`/etc. units). * I think there was general agreement that the case where a font is downloaded for the `ch` unit but would not otherwise be downloaded is extremely rare. (I also argued that a big piece of what makes it rare is the "would not otherwise be used" aspect, which means triggering the download *earlier* when `ch`/etc. units are resolved might actually be a net benefit.) -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3135#issuecomment-1205378100 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 4 August 2022 15:01:09 UTC