- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Dec 2022 22:14:39 +0000
- To: public-css-archive@w3.org
Yeah, talking about parsing in that case doesn't make sense. They should be talking about serialization. If you don't want to elaborate too much on the serialization, just literally doing `s/parsed/serialized/` will be correct without changing the level of detail. Making font-family readonly if possible would probably be best, if we don't want to invoke the CSS parser. Otherwise we'll have to, hmm, invoke [strictly split a string](https://infra.spec.whatwg.org/#strictly-split), then [strip whitespace](https://infra.spec.whatwg.org/#strip-leading-and-trailing-ascii-whitespace) on the parts, before finally interpreting them as font-family names. A lot of trouble for something incredibly low-value to do in the first place! -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8154#issuecomment-1360389142 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 December 2022 22:14:41 UTC