Re: [w3c/selection-api] Selection.direction spec issue, what should happen on multiple click? (Issue #177)

> WebKit also returns none. I'd be rather worried this would be a breaking change.

Yes, it would be a breaking change, but since it does not work properly in Gecko ([bug report](https://bugzilla.mozilla.org/show_bug.cgi?id=1899020#c6)), nor Webkit ([bug report](https://bugs.webkit.org/show_bug.cgi?id=274725#c4)) and it hasn't shipped to chromium yet, I don't think that it would currently break any website.

My concern is, that I do believe that the only use case where the `direction` property would be useful is to determine whether the `anchor` is before, after, or equal with the `focus` boundary-point.

I've been actively working with on a `contenteditable` for a while and as the `direction` currently works, I can't see any advantage of it and I couldn't think to a case where I could use it as it's implemented right now.

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

Message ID: <w3c/selection-api/issues/177/2136828024@github.com>