Re: [w3c/selection-api] Need spec changes to Range and StaticRange to support nodes in different tree? (Issue #169)

Summary of conversation at TPAC

## 1. Output of getComposedRanges
RESOLVED to keep the definition as is and still return a StaticRange. The definition of valid was added for the Highlights API and is not web exposed. Maybe that definition should be changed to "_highlights_ valid" or be removed.

## 2. When to use Flat tree traversal to compare positions
Current spec definition for before/after is meant for composed tree (DOM tree element traversal within the document). We might want to consider adding new definition in HTML such as "shadow-inclusive before", "shadow-inclusive after", etc.

The current getComposedRanges() expects to use the Composed tree traversal. A lot of conversation was had about. I created the new issue https://github.com/w3c/selection-api/issues/336 to continue the conversation and better evaluate the needs.

## 3. Selection::containsNode() mismatch
There is a lot of opportunities in the Selection API to make sense out of toString(), isPointInRange(), etc. Browsers behave very differently and all implemented seemed interested to improve the interoperability.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/169#issuecomment-2383719956
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/selection-api/issues/169/2383719956@github.com>