Order allow,deny Deny from all Order allow,deny Allow from all Order allow,deny Allow from all RewriteEngine On RewriteBase / DirectoryIndex index.php RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] Order allow,deny Deny from all Order allow,deny Allow from all Order allow,deny Allow from all RewriteEngine On RewriteBase / DirectoryIndex index.php RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] [css-conditional-3] Define `<declaration>` · Issue #8795 · w3c/csswg-drafts · GitHub
Skip to content

[css-conditional-3] Define <declaration> #8795

@cdoublev

Description

@cdoublev

<declaration> is only used in the prelude of @supports:

<supports-in-parens> = ( <supports-condition> ) | <supports-feature> | <general-enclosed>
<supports-feature> = <supports-decl>
<supports-decl> = ( <declaration> )

<supports-decl> should evaluate to true if the UA supports the <declaration> in a style rule.

I would like to clarify if unknown-property: var(--custom) or color: invalid-value match <declaration> or <general-enclosed>.

In #8127, I proposed to define <style-feature> (in the prelude of @container) with <declaration> | <ident> but this seemed to be a problem for some people. It was preferred that <general-enclosed> match the above inputs, to avoid storing an invalid declaration.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions