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

Another issue with this potential name change: The beforeInput/Input event will be triggered also on Input fields and textareas. These fields do not have selections that can be expressed as ranges. For most edit types this shouldn't matter, because the taregtRanges will be null anyway. But in the case that one would expect target ranges (fx, when using the spell checker in a textarea), this will be an issue.

I consulted @ojanvafai briefly about this, and he suggested to just let the targetRange always be null in the case of textareas and input fields. 

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