Re: [editing] change of event names beforeInput -> beforeEdit -> beforeInput? (#87)

> Removing "input" from contentEditable=true is not an option. There is a lot of content that depends on it.

I agree with this.

> The two options that are being considered are:
> A. Fire beforeEdit/edit/input on all contentEditable elements and only fire input on textarea/input elements.
> B. Fire beforeInput/input on all contentEditabe, textarea and input elements.

I think that (B) must be the best choice for backward compatibility. As I said above, browser cannot get rid of input event, anyway. So, even if it's defined as "shouldn't be fired on XXX", browsers cannot do that for keeping compatibility with existing websites.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/87#issuecomment-137362932