- From: Johannes Wilm <notifications@github.com>
- Date: Mon, 25 May 2015 10:10:56 -0700
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Monday, 25 May 2015 17:11:26 UTC
As for custom events: We already have ways to listen for key clicks in Javascript and it is fairly easy to have set up one way of listening to a series of key combinations and then initiate various things, such as "Save", "go to next", "close", etc. . Maybe there are other good use cases for this that I cannot think off, but it seems like that should then be a spec of its own and not depend on whether or not there is a contenteditable=typing element on the page. I will close this for now, but please reopen if this has been misunderstood. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/30#issuecomment-105271603
Received on Monday, 25 May 2015 17:11:26 UTC