Skip to content

[css-highlight-api-1] Clarifying that user agents must not use live ranges internally for static ranges #4597 #6545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 1, 2021
Merged

[css-highlight-api-1] Clarifying that user agents must not use live ranges internally for static ranges #4597 #6545

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ed1a7a8
Add note clarifying that user agents must not use live ranges interna…
dandclark Aug 25, 2021
d6a011c
Use spec reference syntax
dandclark Aug 25, 2021
f6cbce0
Pull the note into the normative paragraph.
dandclark Aug 26, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions css-highlight-api-1/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -481,6 +481,8 @@ Range Updating and Invalidation</h3>
the user agent must not adjust the [=boundary points=] of {{StaticRange}}s
in response to DOM changes,
nor can they be modified by the author after creation.
The user agent is expected to store the actual {{StaticRange}}s, rather than backing
them up with live {{Range}}s.

<div class=advisement>
Updating all {{Range}} objects as the DOM is modified
Expand Down