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

Personally, I think the getComposedRanges() API would be much more valuable if it was traversing using a flat tree. I also do agree this is a significant change.
I wonder how hard it would be to change to flat tree if we ship getComposedRanges first using only composed tree?

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

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