[css-highlight-api-1] Clarifying that user agents must not use live ranges internally for static ranges #4597 #6545
Conversation
css-highlight-api-1/Overview.bs
Outdated
| @@ -482,6 +482,9 @@ Range Updating and Invalidation</h3> | |||
| in response to DOM changes, | |||
| nor can they be modified by the author after creation. | |||
|
|
|||
| Note: In other words, the user agent is expected to store the actual | |||
There was a problem hiding this comment.
I would suggest removing the "note :" and combining this with the paragraph above. @frivoal, what do you think?
There was a problem hiding this comment.
I think I'd keep it. To me, this sentence clarifies the intent of this earlier normative sentence, rather than add any new requirement.
the user agent must not adjust the boundary points of StaticRanges in response to DOM changes
Do you think it'd be possible for an implementation to satisfy that requirement while still doing something that would be observably different from using static ranges internally?
There was a problem hiding this comment.
To be clear (in case it wasn't already), my suggestion was just editorial - to combine both the paragraphs into one.
In response to your question though, I think a UA could use live ranges internally and still satisfy the original sentence, since the static ranges created/used by authors wouldn't actually be changed in response to DOM mutations (only the internal live ranges would). That's why I think adding the second sentence is important.
There was a problem hiding this comment.
This makes sense to me:
a UA could use live ranges internally and still satisfy the original sentence, since the static ranges created/used by authors wouldn't actually be changed in response to DOM mutations
I've pulled the text into the above paragraph. Happy to switch it back though, I think either way is reasonable.
There was a problem hiding this comment.
@frivoal @sanketj I just noticed we never landed this.
What can we do to resolve the disagreement here? I'm inclined to agree that it's useful to have this sentence in normative text (not a note). This would specifically forbid the possibility of a UA using live range internally, while not adjusting StaticRanges passed as arguments. Without the new normative sentence, that would arguably be allowed.
There was a problem hiding this comment.
@frivoal Going to go ahead and land this. If there are any objections please let me know and I'll follow up with another PR.
Per resolution in #4597, clarify that when authors uses StaticRange highlights, UAs should use the actual static ranges rather than backing them with live ranges.