- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Mon, 15 Aug 2022 19:18:25 +0000
- To: public-css-archive@w3.org
As @tabatkins [wrote earlier](https://github.com/w3c/csswg-drafts/issues/5969#issuecomment-776373782), the declarations inside `@page` are all descriptors. So regarding custom properties, there are two points that speak _against_ them applying in this context: 1. As their name says, they are custom _properties_, not custom descriptors. 2. Most at-rules like `@page` are outside the normal cascade. Having said that, the spec. defines [cascading within the page context](https://drafts.csswg.org/css-page-3/#cascading-and-page-context). Therefore, it might be possible to allow custom properties (or custom descriptors in this case) within it. Though, as far as I can see, they are not allowed at the moment. Regarding CSS-wide keywords, at least [`inherit` is mentioned to be valid](https://drafts.csswg.org/css-page-3/#page-properties) but the spec. doesn't explicitly mention whether all of them are valid inside the page and margin contexts. Also please note that I am also just interpreting the specifications. @fantasai, @SimonSapin or @tabatkins are the authors of the two relevant specs. Maybe they can confirm whether the statements above are correct. Though I think the specs could benefit from some clarification here. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5969#issuecomment-1215634716 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 15 August 2022 19:18:27 UTC