Re: [w3c/selection-api] `Selection.direction`'s behavior should be based on the node's position (Issue #334)

I haven't clearly mentioned, but the problem is there with the current implementation, that lets say, the user presses the `Shift` + `ArrowRight`, so I have to extend the selection via script, so I set the focus with the `Selection.extend`.

From that point (since the `direction` is not node-position based), when I get the `StaticRange` from the `getComposedRanges` method, I can't know for sure that which one is the focus boundary-point, therefore I will not be able to determine that which node should I extend.



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

Message ID: <w3c/selection-api/issues/334/2291732536@github.com>