Skip to content

Commit 4c3fdb7

Browse files
committed
[css-highlight-api] Remove text for resolved highlight priority issues.
1 parent 0d54afa commit 4c3fdb7

1 file changed

Lines changed: 0 additions & 21 deletions

File tree

css-highlight-api-1/Overview.bs

Lines changed: 0 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -356,27 +356,6 @@ Priority of Overlapping Highlights</h4>
356356
When two ore more [=custom highlights=] have the same numerical priority,
357357
the one most recently [=registered=] has the higher effective [=priority=].
358358

359-
Issue(4593): should negative numbers mean stacking
360-
below the built-in [=highlight pseudo-elements=]?
361-
362-
Issue(4592): Should priority be an (unsigned) integer instead?
363-
That would make comparisons more reliable,
364-
but would likely lead to numbering reminiscent of BASIC line numbers.
365-
366-
Issue(4591): Should we drop priority by numbers entirely,
367-
and replace it with some other ordering mechanism?
368-
Experience with BASIC line number or z-index
369-
does not give much confidence that ordering by number is a good idea.
370-
Is placing in an ordered data-structure better?
371-
Should authors be able to express a desired to be placed above/below
372-
other named highlights,
373-
and let the UA figure it out?
374-
375-
Issue(4594): Should the built-in [=highlight pseudo-elements=]
376-
be exposed as well,
377-
so that they too can be reordered,
378-
and so that they can be interleaved with custom ones freely?
379-
380359
<div class=example id=overlap-highlight-ex>
381360
<xmp highlight=html>
382361
<style>

0 commit comments

Comments
 (0)