A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/w3c/csswg-drafts/issues/8795 below:

[css-conditional-3] Define `<declaration>` · Issue #8795 · w3c/csswg-drafts · GitHub

Skip to content Navigation Menu

Saved searches Use saved searches to filter your results more quickly

Sign up You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Additional navigation options

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

Description

<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.

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3