Re: [w3c/editing] Should execCommand dispatch beforeinput or not? (#200)

@johanneswilm I should may my position clear. I don't agree with dispatching `beforeinput` event for `execCommand`. However, **if** you would declare that `beforeinput` should be dispatched for `execCommand` **and** cancelable, I strongly need to request to declare each `inputType` value of them. The reason is, as you said, Firefox still have minor editing operations which are **not** declared by any spec. Therefore, we will ship `beforeinput` event for them with empty string `inputType` and make them not cancelable. So, I'd like to say that for distinguishing with `beforeinput` event for `execCommand` and the minor operations on Firefox, I need specific `inputType` values for them. In other words, if `beforeinput` event shouldn't be fired for `execComamnd` or not cancelable, I also don't request new `inputType` values for them. Anyway, it does not make sense to make `beforeinput` events whose `inputType` is empty string cancelable because web apps cannot know what each `beforeinput` tells them. So, unless declaring new `inputType` values, why do browsers need to pay the cost of dispatching such useless `beforeinput` event?

-- 
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/editing/issues/200#issuecomment-555781051