- From: tszynalski <notifications@github.com>
- Date: Wed, 15 Jan 2020 04:03:49 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 15 January 2020 12:03:56 UTC
@johanneswilm What you seem to be asking for is a way for a JS app to generate input events which are *indistinguishable* from real input events issued by the user. I'm not sure that should be a design goal at all, given that, for example, JS cannot generate keyboard events that are indistinguishable from the real thing. Generally speaking, I believe you should err on the side of giving developers more information. The reason is simple: If your app doesn't need some piece of information, you can always ignore it. But if you need that piece of information and it's not there, there's nothing you can do. [Above](https://github.com/w3c/editing/issues/200#issuecomment-558949339), I have described an example where it's important to distinguish between user-issued and app-issued `beforeinput` events. You can bet there are many more cases like that. -- 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/editing/issues/200#issuecomment-574630398
Received on Wednesday, 15 January 2020 12:03:56 UTC