Re: [w3c/uievents] A way to determine what the value of an input will be if `beforeinput` is not prevented (#289)

beforeinput doesn't seem all that useful in its current form:
- `data` is always null except for insertions, which makes delete events of limited usefulness
- there is no way of knowing _where_ inside the target value the event is firing

perhaps keyboardevent/beforeinput could include the offset/position of where the event is firing within the target value?

then my users could type "1023", but not "0123".  and it'd mitigate OPs problem a bit, and determine if a deletion occurred in a restricted area.  it'd be nice to get data or something to contain the data that's being removed, however.


-- 
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/uievents/issues/289#issuecomment-977284141