- From: Frederico Caldeira Knabben <notifications@github.com>
- Date: Thu, 23 Apr 2015 09:09:49 -0700
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Thursday, 23 April 2015 16:10:15 UTC
Actually, I think that the overall consensus is to this: > Option 3: (1) completely ignore execCommand and see this as an independent API out of the contenteditable specs and scope. ... added by (2) an eventual warning in the specs that underlines the above. I still don't feel that (2) is necessary, but it should not hurt. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/33#issuecomment-95636025
Received on Thursday, 23 April 2015 16:10:15 UTC