- From: Johannes Wilm <mail@johanneswilm.org>
- Date: Mon, 26 Jun 2017 22:43:37 +0200
- To: "public-editing-tf@w3.org" <public-editing-tf@w3.org>
- Message-ID: <CABkgm-QAgZdzgdLSAMTg1GzWfCsFhrfUCdVB8dXrkktH+7bEgQ@mail.gmail.com>
Hey, the TAG review of the input events spec asked us among other things to convert the long list of inputType values to a table. I have now done that for both levels. Now that I am done I get a clearer picture of which iof the inputTypes the Google people decided to not make cancelable in the level 1 version. They are marked as "Undefined" so that also those implementing level 2 are compliant with level 1. [1] I wonder though -- what made you guys decide to make exactly those not be cancelable? For example, inserting an ordered list can be canceled, but inserting a paragraph break cannot be canceled. Neither one of these should be happening during an IME composition, right? Or if I hit a special key combination to delete a word backward, that cannot be canceled. But if instead I select the word and hit the key combination for cut, that is cancelable. Is this list meant to be final or is this still work in progress? If this is final, then maybe it would be a good idea to write up soem explanation fro the philosophy that lies behind these choices. Otherwise I am sure a lot of JS devs will be just as confused as me about this. [1] https://rawgit.com/w3c/input-events/v1/index.html#h-interface-inputevent-attributes -- Johannes Wilm http://www.johanneswilm.org tel: +1 (520) 399 8880
Received on Monday, 26 June 2017 20:44:10 UTC