- From: Ryosuke Niwa <notifications@github.com>
- Date: Sun, 04 Jan 2015 20:39:36 -0800
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Monday, 5 January 2015 04:40:05 UTC
Like Ben, I don't understand the point of disabling execCommand either since execCommand is a legacy API and there is literally no hope for removing it in any foreseeable future. Disallowing execCommand completely is, a matter of fact, non-trivial if we allow a selection that crosses editing boundaries to exist (i.e. if we don't force UA to normalize such a selection). --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/33#issuecomment-68667763
Received on Monday, 5 January 2015 04:40:05 UTC