Re: [w3c/selection-api] Limit onselectionchange to Document until known to be needed elsewhere (#75)

> I think Gecko has already done that.

Done what?  We currently only dispatch the selectionchange event on Document, but selectstart is dispatched to all elements, depending on the parent start node for the selection's range.

Also, we haven't shipped this API, but we would like to, so we can change our implementation in whatever way that's needed.  I unfortunately don't have access to reopen this issue, but if restricting the selectionchange handler to Document for now allows us to get to something that we can ship faster, that's ideal.

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

Received on Wednesday, 12 October 2016 16:24:54 UTC