- From: Kevin Babbitt via GitHub <noreply@w3.org>
- Date: Wed, 11 Feb 2026 20:11:17 +0000
- To: public-css-archive@w3.org
Right, sorry, that was a badly chosen example. The main thing I was concerned about was making sure whatever we end up doing doesn't create any new requirements to store unparsed shorthands. In the pending-substitution case, we already have to store the unparsed shorthand, so I suppose `from-shorthand()` would just use that. `toggle()` I'd guess would end up similar if we ever figure out how to do it. For system fonts, Blink stores "pending system font values" for each of the subproperties, which refer to the system font id. So that gives us enough to reconstruct what was specified. Legacy shorthands look to me like a case where Blink would have to store something that we aren't today. But if there's just 1 or 2 of those, I'm not too bothered by that. So on further thought I suppose it's not too much of an issue. -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8055#issuecomment-3886856552 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 February 2026 20:11:18 UTC