Skip to content

Commit cc3a769

Browse files
committed
[css-properties-values-api] Define that clashing @Property rules have last-wins, and that registerProperty() wins over all @Property rules. Fixes w3c#845.
1 parent a5cd596 commit cc3a769

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

css-properties-values-api/Overview.bs

+7-2
Original file line numberDiff line numberDiff line change
@@ -850,6 +850,7 @@ CSSOM {#cssom}
850850
return the result.
851851
</div>
852852

853+
853854
The <dfn>@property</dfn> rule {#at-property-rule}
854855
=================================================
855856

@@ -884,8 +885,12 @@ if it's missing, the entire rule is invalid and must be ignored.
884885
If an ''@property'' rule contains any unknown descriptors,
885886
the entire rule is invalid and must be ignored.
886887

887-
Issue(845): What happens when we have both an ''@property'' rule, and a
888-
{{registerProperty()}} call for the same property?
888+
If multiple valid ''@property'' rules are defined for the same <<custom-property-name>>,
889+
the last one in stylesheet order "wins".
890+
A custom property registration from {{CSS/registerProperty|CSS.registerProperty()}}
891+
further wins over any ''@property'' rules
892+
for the same <<custom-property-name>>.
893+
889894

890895
Issue(846): What happens when ''@property'' appears inside a shadow tree?
891896

0 commit comments

Comments
 (0)