Skip to content

Commit 3a24540

Browse files
committed
[css-typed-om] Markup typo, and rewrite note to make more sense.
1 parent f7472af commit 3a24540

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

css-typed-om/Overview.bs

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -484,7 +484,7 @@ probably in an appendix.
484484
1. If |property| is not a [=custom property name string=],
485485
set |property| to |property| [=ASCII lowercased=].
486486

487-
2. If |property| is not a [[=valid CSS property=],
487+
2. If |property| is not a [=valid CSS property=],
488488
[=throw=] a {{TypeError}}.
489489

490490
3. If |property| is a [=single-valued property=] and |values| has more than one [=list/item=],
@@ -498,12 +498,11 @@ probably in an appendix.
498498
and one or more of the [=list/items=] are a {{CSSUnparsedValue}} or {{CSSVariableReferenceValue}} object,
499499
[=throw=] a {{TypeError}}.
500500

501-
Note: When a property is set via string-based APIs,
502-
the presence of ''var()'' in a property
503-
prevents the entire thing from being interpreted.
504-
In other words,
505-
everything *besides* the ''var()'' is a plain [=component value=],
506-
not a meaningful type.
501+
Note: Having 2+ values implies that you're setting multiple items of a list-valued property,
502+
but the presence of a ''var()'' function in the string-based OM disables all syntax parsing,
503+
including splitting into individual iterations
504+
(because there might be more commas inside of the ''var()'' value,
505+
so you can't tell how many items are actually going to show up).
507506
This step's restriction preserves the same semantics in the Typed OM.
508507

509508
5. Let |props| be the value of |this|’s {{[[declarations]]}} internal slot.

0 commit comments

Comments
 (0)