@@ -32,6 +32,8 @@ Status: ED
32
32
Work Status : exploring
33
33
Group : csswg
34
34
ED : https://drafts.csswg.org/css-highlight-api-1/
35
+ TR : https://www.w3.org/TR/css-highlight-api-1/
36
+ Previous Version : https://www.w3.org/TR/2020/WD-css-highlight-api-1-20201022/
35
37
Editor : Florian Rivoal, On behalf of Bloomberg, https://florian.rivoal.net/, w3cid 43241
36
38
Editor : Sanket Joshi, Microsoft Corporation https://www.microsoft.com, https://github.com/sanketj
37
39
Editor : Megan Gardner, Apple Inc. https://apple.com/
@@ -181,7 +183,7 @@ Creating Custom Highlights</h3>
181
183
<li>
182
184
Let |highlight| be the new {{Highlight}} object.
183
185
<li>
184
- If {{name!!argument}} does not [=CSS/parse=] as an <<ident-token>> , then [=throw=] a {{"SyntaxError"}} .
186
+ If {{name!!argument}} does not [=CSS/parse=] as an <<ident-token>> , then [=throw=] a {{"SyntaxError"}} .
185
187
<li>
186
188
Let |nameArg| be the result of [=converted to an ECMAScript value|converting=] {{name!!argument}} to an ECMAScript value.
187
189
<li>
@@ -367,7 +369,7 @@ Priority of Overlapping Highlights</h4>
367
369
Should authors be able to express a desired to be placed above/below
368
370
other named highlights,
369
371
and let the UA figure it out?
370
-
372
+
371
373
Issue(4594): Should the built-in [=highlight pseudo-elements=]
372
374
be exposed as well,
373
375
so that they too can be reordered,
@@ -515,7 +517,7 @@ Range Updating and Invalidation</h3>
515
517
516
518
<h2 id=events>
517
519
Event Handling</h2>
518
-
520
+
519
521
Issue: Section on Events TBD, based on https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/events-explainer.md
520
522
521
523
Issue: should custom highlights have a dedicated event handling mechanism,
0 commit comments