- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Aug 2023 09:40:51 +0000
- To: public-css-archive@w3.org
Thanks for both feedback. Maybe I should have created two separate issues... I was pretty confident that it was an oversight for `@try`. Would it work if custom properties are accepted only if there is one or more declaration of the other accepted properties? I move this question in a separate issue. Based on current interoperability, it seems to be required to define that they are valid in `@page`. I am not sure if these modifications would be enough: ```diff 4.3. @page rule grammar [...] In addition, the following rules apply: - - The @page rule can only contain page properties and margin at-rules. - - The margin at-rules can only contain page-margin properties. + - The @page rule can only contain page and custom properties and margin at-rules. + - The margin at-rules can only contain page-margin and custom properties. [...] 4.4. Cascading in the page context [...] + Custom properties inherits from '':root''. ``` -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9150#issuecomment-1680288039 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 August 2023 09:40:53 UTC