CSS defines a comprehensive set of properties that can be manipulated in order to modify the layout, paint, or behaviour of a web document. However, web authors frequently wish to extend this set with additional properties.
[css-variables] provides primitive means for defining user-controlled properties, however these properties always take token lists as values, must always inherit, and can only impact document layout or paint by being re-incorporated into the value of other properties via a var() reference.
This specification extends [css-variables], allowing the registration of properties that have a value type, an initial value, and a defined inheritance behaviour, via two methods:
A JS API, the registerProperty() method
A CSS at-rule, the @property rule
This specification is complementary to [css-paint-api-1] and [css-layout-api-1], which allow custom properties to directly impact paint and layout behaviours respectively.
2. Registered Custom PropertiesA custom property can become a registered custom property, making it act more like a UA-defined property: giving it a syntax that’s checked by the UA, an initial value, and a specific inheritance behavior. This can be done by the @property rule, or the registerProperty() JS function.
A custom property is considered to be registered for a Document if there is a valid @property rule defined for its name in one of the document’s stylesheets, or its name is contained in the document’s [[registeredPropertySet]] slot (that is, registerProperty() was called to register it).
A registered custom property acts similarly to an unregistered custom property, except as defined below.
2.1. Determining the RegistrationA registered custom property has a custom property registration that contains all the data necessary to treat it like a real property. It’s a struct consisting of:
a property name (a custom property name string)
a syntax (a syntax string)
an inherit flag (a boolean)
optionally, an initial value (a string which successfully parses according to the syntax)
If the Document’s [[registeredPropertySet]] slot contains a record with the custom property’s name, the registration is that record.
Otherwise, if the Document’s active stylesheets contain at least one valid @property rule representing a registration with the custom property’s name, the last such one in document order is the registration.
Otherwise there is no registration, and the custom property is not a registered custom property.
2.2. Parse-Time BehaviorRegistered custom properties parse exactly like unregistered custom properties; almost anything is allowed. The registered syntax of the property is not checked at parse time.
Note: However, the syntax is checked at computed-value time, before substitution via var(). See § 2.4 Computed Value-Time Behavior.
Why aren’t custom properties syntax-checked?When parsing a page’s CSS, UAs commonly make a number of optimizations to help with both speed and memory.
One of those optimizations is that they only store the properties that will actually have an effect; they throw away invalid properties, and if you write the same property multiple times in a single declaration block, all but the last valid one will be thrown away. (This is an important part of CSS’s error-recovery and forward-compatibility behavior.)
This works fine if the syntax of a property never changes over the lifetime of a page. If a custom property is registered, however, it can change its syntax, so that a property that was previously invalid suddenly becomes valid.
The only ways to handle this are to either store every declaration, even those that were initially invalid (increasing the memory cost of pages), or to re-parse the entire page’s CSS with the new syntax rules (increasing the processing cost of registering a custom property). Neither of these are very desirable.
Further, UA-defined properties have their syntax determined by the version of the UA the user is viewing the page with; this is out of the page author’s control, which is the entire reason for CSS’s error-recovery behavior and the practice of writing multiple declarations for varying levels of support. A custom property, on the other hand, has its syntax controlled by the page author, according to whatever stylesheet or script they’ve included in the page; there’s no unpredictability to be managed. Throwing away syntax-violating custom properties would thus only be, at best, a convenience for the page author, not a necessity like for UA-defined properties.
2.3. Specified Value-Time BehaviorJust like unregistered custom properties, all registered custom properties, regardless of registered syntax, accept the CSS-wide keywords, such as inherit or revert. Their behavior is defined in CSS Cascading 4 § 7.3 Explicit Defaulting.
2.4. Computed Value-Time BehaviorThe computed value of a registered custom property is determined by the syntax of its registration.
If the registration’s syntax is the universal syntax definition, the computed value is the same as for unregistered custom properties (either the specified value with variables substituted, or the guaranteed-invalid value).
Otherwise, attempt to parse the property’s value according to its registered syntax. If this fails, the declaration is invalid at computed-value time and the computed value is determined accordingly. If it succeeds, the computed value depends on the specifics of the syntax:
For "<length>", "<length-percentage>", "<angle>", "<time>", "<resolution>", "<integer>", "<number>", and "<percentage>" values:
If the specified value is a dimension literal (such as 50em or .2s), the computed value is the same value, but with the unit converted to the corresponding canonical unit for the type of value.
If the specified value is any other numeric literal (such as 5 or 20%), the computed value is as specified. (In particular, percentages are never resolved against anything.)
If the specified value is a function that evaluates to one of those types (such as a math function), the computed value is defined by that function.
For "<string>" values, the computed value is as specified.
For "<color>" values, the value is computed by resolving color values, per CSS Color 4 § 14. Resolving <color> Values.
For "<custom-ident>", ident, or "*" values, the computed value is as specified.
For "<url>" values, the computed value is one of the following:
if the URL is a relative URL, the computed value is the resolved absolute URL as described in [css3-values].
otherwise, the computed value is as specified.
Because URLs resolve against the base URL of the stylesheet they appear in, we can end up with multiple relative URLs that resolve against different base URLs, even though they appear in the same property.
For example, suppose --url-foo and --url-bar are registered custom properties with <url> syntax, and that we have a stylesheet at /style/foo/foo.css:
div {
--url-foo: url("foo.png");
}
and another stylesheet at /style/bar/bar.css
div {
--url-bar: url("bar.png");
}
and finally a document at /index.html:
<link href="/style/foo/foo.css" rel="stylesheet" type="text/css"> <link href="/style/bar/bar.css" rel="stylesheet" type="text/css"> <div style="background-image: var(--url-foo), var(--url-bar);"> </div>
Here, the var(--url-foo) reference would produce a URL that resolves against /style/foo, and the var(--url-bar) reference would produce a URL that resolves against /style/bar.
On the other hand, if both --url-foo and --url-bar were unregistered, they would substitute their literal values (relative URLs) into the /index.html stylesheet, which would then resolve the URLs against /index.html instead.
For "<image>" values, the computed value is the computed <image>.
For "<transform-function>" and "<transform-list>" values, the computed value is as specified but with all lengths resolved to their computed values.
For values with multipliers, the computed value is a list of the computed values of the base type.
For syntaxes specified with the | combinator, the computed value is given by applying the computed-value rules for the first clause that matches the value.
2.5. Animation BehaviorNote: As defined by [css3-animations] and [css3-transitions], it is possible to specify animations and transitions that reference custom properties.
When referenced by animations and transitions, custom property values interpolate by computed value, in accordance with the type that they parsed as.
Note: This implies that a list of values, such as <color>+ or <color>#, will interpolate as a simple list, matching up each component index-by-index, and failing if the number of components doesn’t match.
As an exception to the above rule, a value that parsed as a <transform-list>, a <transform-function>, or a <transform-function>+ instead interpolates as per the transform property.
Note: If, for whatever reason, a custom property is defined with a syntax of <transform-function>#, this will thus first interpolate as a simple list, and then each list item will interpolate as a transform value.
Note: Registering (or changing the registration) of a custom property can change its computed value, which can start or interrupt a CSS transition.
2.6. Conditional RulesAs stated in § 2.2 Parse-Time Behavior, both unregistered and registered custom properties accept (almost) all possible values at parse-time. Registered custom properties only apply their syntax at computed value time.
So, all custom properties, regardless of whether they’re registered or unregistered, will test as "true" in an @supports rule, so long as you don’t violate the (very liberal) generic syntax for custom properties.
For example, even if a custom property is registered with
syntax : "<color>" ;
, a rule like
@supports (--foo: 1em) {...}
will still evaluate as true and apply those styles, because the declaration
doessuccessfully parse as a valid property.
2.7. Substitution via var()Like unregistered custom properties, the value of a registered custom property can be substituted into another value with the var() function. However, registered custom properties substitute as their computed value, rather than the original token sequence used to produce that value.
Any var() function that references a registered custom property must be replaced with an equivalent token sequence, which is equal to the token sequence that would have been produced by serializing the computed value, and tokenizing the resulting string.
Suppose that
--xis registered with
<length>syntax, and that
--yis an unregistered custom property.
div {
font-size: 10px;
--x: 8em;
--y: var(--x);
}
Because the computed value of --x (when serialized) is "80px", the computed value of --y is a <dimension-token> with a value of "80" and unit "px".
2.7.1. Dependency Cycles via Relative UnitsRegistered custom properties follow the same rules for dependency cycle resolution as unregistered custom properties, with the following additional constraints:
For any registered custom property with a <length> or <length-percentage> syntax component:
If the property contains any of the following units: em, ex, cap, ch, ic, lh; then add an edge between the property and the font-size of the current element.
If the property contains the lh unit, add an edge between the property and the line-height of the current element.
If the property contains any of the following units: rem, rlh; then add an edge between the property and the font-size' of the root element.
If the property contains the rlh unit, add an edge between the property and the line-height' of the root element.
For example, given this registration:
CSS.registerProperty({
name: "--my-font-size",
syntax: "<length>",
initialValue: "0px",
inherits: false
});
the following will produce a dependency cycle:
div {
--my-font-size: 10em;
font-size: var(--my-font-size);
}
and font-size will behave as if the value unset was specified.
2.8. Shadow DOMUnlike many concepts in CSS (see CSS Scoping 1 § 2.5 Name-Defining Constructs and Inheritance), property registrations are not scoped to a tree scope. All registrations, whether they appear in the outermost document or within a shadow tree, interact in a single global registration map for the Document.
There are clear use-cases for property registrations to be scoped—a component using Shadow DOM and registering some custom properties for its own internal use probably doesn’t intend for the outer page to see the registration, since the outer page doesn’t even know the component is using that property.
However, there are also reasons to not scope the registration—custom properties are used to pipe data into a component, and it’s useful for the outer page to be able to set such custom properties and have them syntax-checked by the registration; similarly, concepts such as a property’s initial value don’t make much sense unless the property registration exists globally, so it applies to the property even at the document’s root.
But the above just means that registration scope might be something that should be controllable, not that it should be forced to be global.
The reason registrations must be global is because elements can exist in multiple tree scopes at the same time, with styles from each tree scope intermingling and cascading together. This applies to the host element, which lives in the outer tree but is stylable from the shadow tree by the :host selector, but also elements inside a shadow DOM that are targetable from the outer tree by the ::part() pseudo-element.
If registrations could be scoped to a tree scope, and a single property was registered both inside and outside, it’s not clear which registration should be applied to parse the value. Even if we tracked which tree a value came from (something we do for other tree-scoped values) and applied the corresponding registration, it’s not clear that this would give a reasonable result—the shadow DOM might expect a property to have a particular value space, and be surprised when it receives something completely different due to the outer tree winning the cascade and applying its own registration.
When custom properties are exposed as part of a Shadow DOM-using component’s public API, this global registration behavior works as intended. If the outer page is using a custom property of the same name for different purposes, that is already a conflict that needs to be resolved, and the registration behavior does not make it worse.
If a custom property is intended for private internal usage for a component, however, it is recommended that the property be given a likely-unique name, to minimize the possibility of a clash with any other context. This can be done, for example, by including the project name, or some short random string of text, in the name of the property.
3. The @property RuleThe @property rule represents a custom property registration directly in a stylesheet without having to run any JS. Valid @property rules result in a registered custom property, as if registerProperty() had been called with equivalent parameters.
The syntax of @property is:
@property <custom-property-name> {
<declaration-list>
}
A valid @property rule represents a custom property registration, with the property name being the serialization of the <custom-property-name> in the rule’s prelude.
@property rules require a syntax and inherits descriptor; if either are missing, the entire rule is invalid and must be ignored. The initial-value descriptor is optional only if the syntax is the universal syntax definition, otherwise the descriptor is required; if it’s missing, the entire rule is invalid and must be ignored.
Unknown descriptors are invalid and ignored, but do not invalidate the @property rule.
Note: As specified in § 2.1 Determining the Registration, if multiple valid @property rules are defined for the same <custom-property-name>, the last one in stylesheet order "wins". A custom property registration from CSS.registerProperty() further wins over any @property rules for the same <custom-property-name>.
Specifies the syntax of the custom property registration represented by the @property rule, controlling how the property’s value is parsed at computed value time.
The syntax descriptor is required for the @property rule to be valid; if it’s missing, the @property rule is invalid.
If the provided string is not a valid syntax string (if it returns failure when consume a syntax definition is called on it), the descriptor is invalid and must be ignored.
3.2. The inherits Descriptor Name: inherits For: @property Value: true | false Initial: n/a (see prose)Specifies the inherit flag of the custom property registration represented by the @property rule, controlling whether or not the property inherits by default.
The inherits descriptor is required for the @property rule to be valid; if it’s missing, the @property rule is invalid.
3.3. The initial-value DescriptorSpecifies the initial value of the custom property registration represented by the @property rule, controlling the property’s initial value.
If the value of the syntax descriptor is the universal syntax definition, then the initial-value descriptor is optional. If omitted, the initial value of the property is the guaranteed-invalid value.
Otherwise, if the value of the syntax descriptor is not the universal syntax definition, the following conditions must be met for the @property rule to be valid:
The initial-value descriptor must be present.
The initial-value descriptor’s value must parse successfully according to the grammar specified by the syntax definition.
The initial-value must be computationally independent.
If the above conditions are not met, the @property rule is invalid.
4. Registering Custom Properties in JSTo register a custom property via JS, the CSS object is extended with a registerProperty() method:
dictionary PropertyDefinition {
required DOMString name;
DOMString syntax = "*";
required boolean inherits;
DOMString initialValue;
};
partial namespace CSS {
undefined registerProperty(PropertyDefinition definition);
};
Additional, the Document object gains a new [[registeredPropertySet]] private slot, which is a set of records that describe registered custom properties.
registerProperty() Function
The registerProperty(PropertyDefinition definition) method registers a custom property according to the configuration options provided in definition. When it is called, it executes the register a custom property algorithm, passing the options in its definition argument as arguments of the same names.
To
register a custom propertywith
namebeing a string, and optionally
syntaxbeing a string,
inheritsbeing a boolean, and
initialValuebeing a string, execute these steps:
Let property set be the value of the current global object’s associated Document’s [[registeredPropertySet]] slot.
If name is not a custom property name string, throw a SyntaxError and exit this algorithm.
If property set already contains an entry with name as its property name (compared codepoint-wise), throw an InvalidModificationError and exit this algorithm.
Attempt to consume a syntax definition from syntax. If it returns failure, throw a SyntaxError. Otherwise, let syntax definition be the returned syntax definition.
If syntax definition is the universal syntax definition, and initialValue is not present, let parsed initial value be empty. This must be treated identically to the "default" initial value of custom properties, as defined in [css-variables]. Skip to the next step of this algorithm.
Otherwise, if syntax definition is the universal syntax definition, parse initialValue according to <declaration-value>?. If this fails, throw a SyntaxError and exit this algorithm. Otherwise, let parsed initial value be the parsed result. Skip to the next step of this algorithm.
Otherwise, if initialValue is not present, throw a SyntaxError and exit this algorithm.
Otherwise, parse initialValue according to syntax definition. If this fails, throw a SyntaxError and exit this algorithm.
Otherwise, let parsed initial value be the parsed result. If parsed initial value is not computationally independent, throw a SyntaxError and exit this algorithm.
Set inherit flag to the value of inherits.
Let registered property be a struct with a property name of name, a syntax of syntax definition, an initial value of parsed initial value, and an inherit flag of inherit flag. Append registered property to property set.
A property value is computationally independent if it can be converted into a computed value using only the value of the property on the element, and "global" information that cannot be changed by CSS.
For example,
5pxis
computationally independent, as converting it into a computed value doesn’t change it at all. Similarly,
1inis
computationally independent, as converting it into a computed value relies only on the "global knowledge" that
1inis
96px, which can’t be altered or adjusted by anything in CSS.
On the other hand, 3em is not computationally independent, because it relies on the value of font-size on the element (or the element’s parent). Neither is a value with a var() function, because it relies on the value of a custom property.
When a custom property is registered with a given type, the process via which specified values for that property are turned into computed values is defined fully by the type selected, as described in § 2.4 Computed Value-Time Behavior.
Note: A way to unregister properties may be added in the future.
Registering a custom property must not affect the cascade in any way. Regardless of what syntax is specified for a registered property, at parse time it is still parsed as normal for a custom property, accepting nearly anything. If the specified value for a registered custom property violates the registered syntax, however, the property becomes invalid at computed-value time (and thus resets to the registered initial value).
By default, all custom property declarations that can be parsed as a sequence of tokens are valid. Hence, the result of this stylesheet:
.thing {
--my-color: green;
--my-color: url("not-a-color");
color: var(--my-color);
}
is to set the color property of elements of class "thing" to inherit. The second --my-color declaration overrides the first at parse time (both are valid), and the var() reference in the color property is found to be invalid at computed-value time (because url("not-a-color") is not a color). At this stage of the CSS pipeline (computation time), the only available fallback is the initial value of the property, which in the case of color is inherit. Although there was a valid usable value (green), this was removed during parsing because it was superseded by the URL.
If we call:
CSS.registerProperty({
name: "--my-color",
syntax: "<color>",
initialValue: "black",
inherits: false
});
the parsing doesn’t significantly change, regardless of whether the registration occurs before or after the stylesheet above. The only difference is that it’s the --my-color property that becomes invalid at computed-value time instead and gets set to its initial value of black; then color is validly set to black, rather than being invalid at computed-value time and becoming inherit.
4.2. ThePropertyDefinition Dictionary
A PropertyDefinition dictionary represents author-specified configuration options for a custom property. PropertyDefinition dictionaries contain the following members:
name, of type DOMString
The name of the custom property being defined.
syntax, of type DOMString, defaulting to "*"
A string representing how this custom property is parsed.
inherits, of type boolean
True if this custom property should inherit down the DOM tree; False otherwise.
initialValue, of type DOMString
The initial value of this custom property.
A syntax string describes the value types accepted by a registered custom property. Syntax strings consists of syntax component names, that are optionally multiplied and combined.
A syntax string can be parsed into a syntax definition, which is either:
A list of syntax components, each of which accept the value types specified in § 5.1 Supported Names, or
The universal syntax definition (*), which accepts any valid token stream.
Note: Regardless of the syntax specified, all custom properties accept CSS-wide keywords, and process these values appropriately.
For example, the following are all valid syntax strings.
"<length>"
accepts length values
"<length> | <percentage>"
accepts lengths, percentages, percentage calc expressions, and length calc expressions, but not calc expressions containing a combination of length and percentage values.
"<length-percentage>"
accepts all values that "<length> | <percentage>" would accept, as well as calc expressions containing a combination of both length and percentage values.
"big | bigger | BIGGER"
accepts the ident big, or the ident bigger, or the ident BIGGER.
"<length>+"
accepts a space-separated list of length values.
accepts any valid token stream
Note: The internal grammar of syntax strings is a subset of the CSS Value Definition Syntax. Future levels of this specification are expected to expand the complexity of the allowed grammar, allowing custom properties that more closely resemble the full breadth of what CSS properties allow.
The remainder of this chapter describes the internal grammar of the syntax strings.
5.1. Supported NamesThis section defines the supported syntax component names, and the corresponding types accepted by the resulting syntax component.
Any valid <length> value
<number> values
Any valid <percentage> value
Any valid <length> or <percentage> value, any valid <calc()> expression combining <length> and <percentage> components.
Any valid <string> value
Any valid <color> value
Any valid <image> value
Any valid <url> value
Any valid <integer> value
Any valid <angle> value
Any valid <time> value
Any valid <resolution> value
Any valid <transform-function> value
Any valid <custom-ident> value
That identifier
Note: <custom-ident>s are compared codepoint-wise with each other; this is different than the normal behavior of UA-defined CSS which limits itself to ASCII and is ASCII case-insensitive. So, specifying an ident like Red means that the precise value Red is accepted; red, RED, and any other casing variants are not matched by this. It is recommended that idents be restricted to ASCII and written in lower-case, to match CSS conventions.
A list of valid <transform-function> values. Note that "<transform-list>" is a pre-multiplied data type name equivalent to "<transform-function>+"
Note: A syntax string of "*" will produce the universal syntax definition, which is not a syntax component. Therefore, "*" may not be multiplied or combined with anything else.
Any syntax component name except pre-multiplied data type names may be immediately followed by a multiplier:
Indicates a space-separated list.
Indicates a comma-separated list.
"<length>+"
accepts a space-separated list of length values
"<color>#"
accepts a comma-separated list of color values
Note: The multiplier must appear immediately after the syntax component name being multiplied.
5.3. The '|' CombinatorSyntax strings may use U+007C VERTICAL LINE (|) to provide multiple syntax component names. Such syntax strings will result in a syntax definition with multiple syntax components.
When a syntax definition with multiple syntax components is used to parse a CSS value, the syntax components are matched in the order specified.
Note: That is, given the syntax string "red | <color>", matching the value red against it will parse as an identifier, while matching the value blue will parse as a <color>.
"<length> | auto"
accepts a length, or auto
"foo | <color># | <integer>"
accepts foo, a comma-separated list of color values, or a single integer
A sequence of code points consisting of a U+003C LESS-THAN SIGN (<), followed be zero or more ident code points, and terminated by U+003E GREATER-THAN SIGN (>).
A data type name that represents another syntax component with a multiplier already included.
An object consisting of a syntax component name, and an optional multiplier.
A sequence of code points which is either a data type name, or a sequence that can produce a <custom-ident>.
An object consisting of a list of syntax components.
A special syntax definition which accepts any valid token stream.
The value specified for a registered custom property is not interpreted until computed-value time. This means that only APIs that retrieve computed values are affected. Other APIs must ignore the
[[registeredPropertySet]]
slot of the associated
Document
, and treat all custom properties as unregistered.
6.1. TheCSSPropertyRule Interface
The CSSPropertyRule interface represents an @property rule.
[Exposed=Window]
interface CSSPropertyRule : CSSRule {
readonly attribute CSSOMString name;
readonly attribute CSSOMString syntax;
readonly attribute boolean inherits;
readonly attribute CSSOMString? initialValue;
};
name, of type CSSOMString, readonly
syntax, of type CSSOMString, readonly
inherits, of type boolean, readonly
initialValue, of type CSSOMString, readonly, nullable
To
serialize a CSSPropertyRule, return the concatenation of the following:
The string "@property" followed by a single SPACE (U+0020).
The result of performing serialize an identifier on the rule’s name, followed by a single SPACE (U+0020).
The string "{ ", i.e., a single LEFT CURLY BRACKET (U+007B), followed by a SPACE (U+0020).
The string "syntax:", followed by a single SPACE (U+0020).
The result of performing serialize a string on the rule’s syntax, followed by a single SEMICOLON (U+003B), followed by a SPACE (U+0020).
The string "inherits:", followed by a single SPACE (U+0020).
For the rule’s inherits attribute, one of the following depending on the attribute’s value:
The string "true" followed by a single SEMICOLON (U+003B), followed by a SPACE (U+0020).
The string "false" followed by a single SEMICOLON (U+003B), followed by a SPACE (U+0020).
If the rule’s initial-value is present, follow these substeps:
The string "initial-value:".
The result of performing serialize a CSS value in the rule’s initial-value followed by a single SEMICOLON (U+003B), followed by a SPACE (U+0020).
A single RIGHT CURLY BRACKET (U+007D).
CSSStyleValue Reification
To
reify a registered custom property valuegiven a property
propertyand
syntax definition syntax, run these steps:
For specified values, reify a list of component values from the value, and return the result.
For computed values:
If the value is a <length>, <integer>, <number>, <angle>, <time>, <resolution>, <percentage> or <length-percentage>; reify a numeric value from the value and return the result.
If the value is a <transform-function>, reify a <transform-function> from the value and return the result.
If the value is a <transform-list>, reify a <transform-list> from the value and return the result.
If the value is an <image>, reify a CSSImageValue from the value and return the result.
If the value is an identifier, reify an identifier from the value and return the result.
If syntax is the universal syntax definition, reify a list of component values from the value, and return the result.
Otherwise, reify as a CSSStyleValue with the [[associatedProperty]] internal slot set to property, and return the result.
<script>
CSS.registerProperty({
name: "--stop-color",
syntax: "<color>",
inherits: false,
initialValue: "rgba(0,0,0,0)"
});
</script>
<style>
.button {
--stop-color: red;
background: linear-gradient(var(--stop-color), black);
transition: --stop-color 1s;
}
.button:hover {
--stop-color: green;
}
</style>
7.2. Example 2: Using @property to register a property
<script>
CSS.paintWorklet.addModule('circle.js');
</script>
<style>
@property --radius {
syntax: "<length>";
inherits: false;
initial-value: 0px;
}
div {
width: 100px;
height: 100px;
--radius: 10px;
background: paint(circle);
transition: --radius 1s;
}
div:hover {
--radius: 50px;
}
</style>
<div></div>
// circle.js
registerPaint('circle', class {
static get inputProperties() { return ['--radius']; }
paint(ctx, geom, properties) {
let radius = properties.get('--radius').value;
ctx.fillStyle = 'black';
ctx.beginPath();
ctx.arc(geom.width / 2, geom.height / 2, radius, 0, 2 * Math.PI);
ctx.fill();
}
});
8. Security Considerations
There are no known security issues introduced by these features.
9. Privacy ConsiderationsThere are no known privacy issues introduced by these features.
10. Changes 10.1. Changes since the Working Draft of 13 October 2020/* to 20 March 2024 */
Made "initial-value" have a <declaration-value>?, same as custom properties. (#9078)
Allowed @Property in shadow trees. (#1085)
Added section explaining why property registration is global, rather than shadow-scoped.
Exported the terms "registered custom property" and "universal syntax definition", for use in other specifications. (#1020)
Used the term "invalid at computed-value time" rather than "guaranteed-invalid value".
Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.
All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:
Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:
Note, this is an informative note.
Advisements are normative sections styled to evoke special attention and are set apart from other normative text with <strong class="advisement">, like this: UAs MUST provide an accessible alternative.
A style sheet is conformant to this specification if all of its statements that use syntax defined in this module are valid according to the generic CSS grammar and the individual grammars of each feature defined in this module.
A renderer is conformant to this specification if, in addition to interpreting the style sheet as defined by the appropriate specifications, it supports all the features defined by this specification by parsing them correctly and rendering the document accordingly. However, the inability of a UA to correctly render a document due to limitations of the device does not make the UA non-conformant. (For example, a UA is not required to render color on a monochrome monitor.)
An authoring tool is conformant to this specification if it writes style sheets that are syntactically correct according to the generic CSS grammar and the individual grammars of each feature in this module, and meet all other conformance requirements of style sheets as described in this module.
So that authors can exploit the forward-compatible parsing rules to assign fallback values, CSS renderers must treat as invalid (and ignore as appropriate) any at-rules, properties, property values, keywords, and other syntactic constructs for which they have no usable level of support. In particular, user agents must not selectively ignore unsupported component values and honor supported values in a single multi-value property declaration: if any value is considered invalid (as unsupported values must be), CSS requires that the entire declaration be ignored.
Once a specification reaches the Candidate Recommendation stage, non-experimental implementations are possible, and implementors should release an unprefixed implementation of any CR-level feature they can demonstrate to be correctly implemented according to spec.
To establish and maintain the interoperability of CSS across implementations, the CSS Working Group requests that non-experimental CSS renderers submit an implementation report (and, if necessary, the testcases used for that implementation report) to the W3C before releasing an unprefixed implementation of any CSS features. Testcases submitted to W3C are subject to review and correction by the CSS Working Group.
No properties defined.
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