Re: [w3c/uievents] Should require Input event to be fired within same event loop as keydown? keypress? neither? (#238)

Hmm.. I guess I was answering the question from the title "should input be in same event loop as keypress" with "we could define input in same loop as keydown; and keypress in same loop as keydown" (or something like that) so that the definitions are relative to non-deprecated events.

But once there's a proper algorithm, then it doesn't make sense to think of it that way. Since it would be written more like:

* fire keydown in event loop X
* fire input in event loop X
* fire keypress in event loop X

Sorry about the confusion there. To more directly answer your question, we can't remove `keypress` and it needs to be included in the spec, I just want to ensure that it can (in theory) be removed without breaking the spec.

-- 
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/238#issuecomment-668719726