Re: [w3c/selection-api] Specify Selection.modify()? (#37)

> Could you explain about "various security concerns"? To make me not to think about calling JS method from C++ in future discussion.

We modify selections in places where it's not safe to invoke JavaScript. This is why we don't have `beforeinput` for selection. `selectstart` event happens to fire in only places where it's safe to dispatch an event.

> Also, if anyone wants to attempts removal, it would be good to confirm with the other two vendors that this is not totally off the table.

Removing this API is off the table for us in the foreseeable future. We should spec this API using the same underlying algorithm as `getSelection().modify` instead of trying to remove it.

It's true that it's not a great layering but TC39 still had to spec `String.prototype.font` for compatibility reasons. Here too, we have to suck it up and spec the API for compatibility reasons.

-- 
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/37#issuecomment-292330234