Re: [w3c/selection-api] Flat Tree or Composed Tree (Issue #336)

After talking with the Blink team, we have come to an agreement that changing the Selection API to use flat tree traversal would be a huge project. The proposal of supporting multiple ranges for Selection is something we cannot implement currently. Adding more APIs should also be considered after a thorough new compatibility investigation. Surveying the existing feature requests, most complaints are about selection across trees not returning the same between browsers and less about specific slot edge cases. Since our goal is to unblock the web developers who depend on the Selection API, we agree to move forward with an implementation of getComposedRanges() using Composed DOM tree traversal.

With all the good conversations so far, it is obvious a flat tree traversal can help solve the discrepancy across browsers when it comes to how elements are selected. Some use cases include selection by dragging and converting a selection to string. We should keep this issue open and continue the discussion.

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

Message ID: <w3c/selection-api/issues/336/2412561709@github.com>