What is the advantage of an API not working in cE=typing? If you don’t want it to work on your site, just don’t call it. Am I missing something? From: Frederico Knabben [mailto:f.knabben@cksource.com] Sent: Monday, December 15, 2014 8:13 AM To: Koji Ishii Cc: Ben Peters; Johannes Wilm; Olivier Forget; public-editing-tf Subject: Re: execCommand and contenteditable=typeing (was Re: Only Text Input and Intention Events On Saturday, 13 December 2014 at 05:39, Koji Ishii wrote: I would prefer execCommand() simply fails if the selection contains contenteditable=typing, and editors do all the work with intentions and possibly with DOM manipulations. I couldn’t agree more. Do we want to make exceptions for some commands that don’t touch the DOM, like execCommand(‘selectAll’)? Actually this may be the one and only case. I would be fine to totally dropping execCommand, for consistency. -- Frederico Knabben CKEditor Project Lead and CKSource Owner -- CKSource - http://cksource.com -- Follow us on: Twitter<http://twitter.com/ckeditor> | Facebook<http://www.facebook.com/ckeditor> | Google+<https://plus.google.com/107736718646302128806> | LinkedIn<http://www.linkedin.com/company/cksource>
Received on Monday, 15 December 2014 21:04:08 UTC