Re: [editing] InputEvent.targetRange in <input> (#72)

I can see your point about the name, and currently it's also specced to work on \<input> fields. But unless this is something really needed to work effectively with textareas/input fields, I would say this isn't really needed.

> If beforeinput only fires on cE elements then maybe it should be called something else.

Possibly yes. Currently there is the `input` event for both cE and relevant \<input> elements, `change` which only works on \<input>-elements, and now we would add this new event which only works on elements that can contain a normal DOM-range selection (so not \<input>-elements). I would almost think it would be more confusing if this event would sometimes throw out one type of range and sometimes a different, and AFAIK there hasn't been the same cry for improvement in the \<input type=text> community as there has been in the cE-community, AFAIK, so unless we can find a usecase where this is really important to have, I think I would advocate for either removing it from \<input> elements AND possibly change the name of it.


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