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

Oh, now I get that why it has to be directionless, thanks!

There is one more thing might worth to mention, in the [User Interactions](https://w3c.github.io/selection-api/#user-interactions):

> set update [selection](https://w3c.github.io/selection-api/#dfn-selection)'s [direction](https://w3c.github.io/selection-api/#dfn-direction) to [forwards](https://w3c.github.io/selection-api/#dfn-forwards) if the [start](https://dom.spec.whatwg.org/#concept-range-start) is [before](https://dom.spec.whatwg.org/#concept-range-bp-before) or equal to the [end](https://dom.spec.whatwg.org/#concept-range-end), [backwards](https://w3c.github.io/selection-api/#dfn-backwards) if if the [end](https://dom.spec.whatwg.org/#concept-range-end) is [before](https://dom.spec.whatwg.org/#concept-range-bp-before) the [start](https://dom.spec.whatwg.org/#concept-range-start)

In this statement, we should refer to anchor and the focus instead of the range's boundary points, aren't we?

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

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