Re: [w3c/selection-api] Pass the original events or add events types in selectionchange (#65)

update: I've been in a situation where I need to know a 'target' for the selection change, or other times I needed an event type that triggered that change in selection.

Since selection change is always triggered by another event (I think), wouldn't it be better to include more information in this event?

I've done things like http://jsfiddle.net/rk6f74tw/34/ (check console and select content either in the blue menu or elsewhere) as also a polyfill, but it's of course more heavy

When using user-select:none CSS property, it doesn't work the same on all browsers, I posted bugs on edge and chrome, only Firefox (nightly, because they forgot to enable selectionchange on current releases) doesn't send selectionchange event on element with user-select:none, which makes sense to me.

https://bugs.chromium.org/p/chromium/issues/detail?id=621543  
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/7938589/

---
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/65#issuecomment-227223228