Skip to content

Commit 99b5d8b

Browse files
committed
[css-highlight-api] prepare for TR then revert to ED
1 parent 9263ecf commit 99b5d8b

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

css-highlight-api-1/Overview.bs

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,8 @@ Status: ED
3232
Work Status: exploring
3333
Group: csswg
3434
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/
3537
Editor: Florian Rivoal, On behalf of Bloomberg, https://florian.rivoal.net/, w3cid 43241
3638
Editor: Sanket Joshi, Microsoft Corporation https://www.microsoft.com, https://github.com/sanketj
3739
Editor: Megan Gardner, Apple Inc. https://apple.com/
@@ -181,7 +183,7 @@ Creating Custom Highlights</h3>
181183
<li>
182184
Let |highlight| be the new {{Highlight}} object.
183185
<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"}}.
185187
<li>
186188
Let |nameArg| be the result of [=converted to an ECMAScript value|converting=] {{name!!argument}} to an ECMAScript value.
187189
<li>
@@ -367,7 +369,7 @@ Priority of Overlapping Highlights</h4>
367369
Should authors be able to express a desired to be placed above/below
368370
other named highlights,
369371
and let the UA figure it out?
370-
372+
371373
Issue(4594): Should the built-in [=highlight pseudo-elements=]
372374
be exposed as well,
373375
so that they too can be reordered,
@@ -515,7 +517,7 @@ Range Updating and Invalidation</h3>
515517

516518
<h2 id=events>
517519
Event Handling</h2>
518-
520+
519521
Issue: Section on Events TBD, based on https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/events-explainer.md
520522

521523
Issue: should custom highlights have a dedicated event handling mechanism,

0 commit comments

Comments
 (0)