- From: Johannes Wilm <notifications@github.com>
- Date: Tue, 16 Aug 2016 14:03:14 -0700
- To: w3c/editing <editing@noreply.github.com>
- Message-ID: <w3c/editing/issues/144/240238049@github.com>
While I can see several thinks working, I think consistency should be important. Without consistency, this will be increasingly difficult to use. For the case where the JS author really wants to cancel the cut, there needs to be a way to do that. And if we don't want JS authors to intercept keydown combinations, and we cannot pass any argument to preventDefault, it seems like preventDefaulting ```beforeinput cut``` has to cancel the clipboard update as well. So A and C seem reasonable from that perspective. The only thing is that in either case is the problem of then getting the changed content into the clipboard. If I recall correctly, the only way of getting something into the clipboard is by adding it to the DOM, then selecting it, then calling ```document.execCommand('copy')``` and removing it from the DOM again (unless one wants it to stay there). IS this still the case? That seems a little bit less than ideal. -- 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/144#issuecomment-240238049
Received on Tuesday, 16 August 2016 21:03:44 UTC