Two deferred to TODOs, the third was bogus (the problem it pointed out
was already removed in the Great Nbsp Rewrite).

editcommands.html

source.html

--- a/editcommands.html Tue Jul 12 15:34:10 2011 -0600+++ b/editcommands.html Tue Jul 12 15:36:39 2011 -0600@@ -6673,11 +6673,13 @@ This is still a huge headache, though. -->-<p class=XXX>This doesn't work well if the input contains things that aren't-supposed to appear in HTML, like carriage returns or nulls. Nor is it going to-work well if the current cursor position is in between two halves of a non-BMP+<!--+TODO: This doesn't work well if the input contains things that aren't supposed+to appear in HTML, like carriage returns or nulls. Nor is it going to work+well if the current cursor position is in between two halves of a non-BMP character. This will result in unserializability. The current spec disregards this, as Chrome 14 dev does.+--> <ol> <li><a href=#delete-the-contents>Delete the contents</a> of the <a href=#active-range>active range</a>.@@ -6701,9 +6703,8 @@ <li>If <var title="">value</var> is a newline (U+00A0), take the <a href=#action>action</a> for <a href=#the-insertparagraph-command>the <code title="">insertParagraph</code> command</a> and abort these steps.-- <p class=XXX>WebKit also does magic for tabs, wrapping them in a- whitespace-preserving span.+ <!-- TODO: WebKit also does magic for tabs, wrapping them in a+ whitespace-preserving span. Should we? --> <li>Let <var title="">node</var> and <var title="">offset</var> be the <a href=#active-range>active range</a>'s <a class=external data-anolis-spec=domrange href=http://html5.org/specs/dom-range.html#concept-range-start title=concept-range-start>start</a> <a class=external data-anolis-spec=domrange href=http://html5.org/specs/dom-range.html#concept-boundary-point-node title=concept-boundary-point-node>node</a> and <a class=external data-anolis-spec=domrange href=http://html5.org/specs/dom-range.html#concept-boundary-point-offset title=concept-boundary-point-offset>offset</a>.@@ -6757,10 +6758,6 @@ <li>If <var title="">node</var> has only one <a class=external data-anolis-spec=domcore href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-tree-child title=concept-tree-child>child</a>, which is a <a href=#collapsed-line-break>collapsed line break</a>, remove its <a class=external data-anolis-spec=domcore href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#concept-tree-child title=concept-tree-child>child</a> from it.- <p class=XXX>This is wrong in all sorts of cases, like- "foo&lt;b&gt;[]&lt;/b&gt;bar". As above, this is hard to get right without heavy- CSS involvement.- <li>Let <var title="">text</var> be the result of calling <code class=external data-anolis-spec=domcore title=dom-Document-createTextNode><a href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#dom-document-createtextnode>createTextNode(<var title="">value</var>)</a></code> on the <a class=external data-anolis-spec=domrange href=http://html5.org/specs/dom-range.html#context-object>context object</a>.

--- a/source.html Tue Jul 12 15:34:10 2011 -0600+++ b/source.html Tue Jul 12 15:36:39 2011 -0600@@ -6670,11 +6670,13 @@ This is still a huge headache, though. -->-<p class=XXX>This doesn't work well if the input contains things that aren't-supposed to appear in HTML, like carriage returns or nulls. Nor is it going to-work well if the current cursor position is in between two halves of a non-BMP+<!--+TODO: This doesn't work well if the input contains things that aren't supposed+to appear in HTML, like carriage returns or nulls. Nor is it going to work+well if the current cursor position is in between two halves of a non-BMP character. This will result in unserializability. The current spec disregards this, as Chrome 14 dev does.+--> <ol> <li><span>Delete the contents</span> of the <span>active range</span>.@@ -6698,9 +6700,8 @@ <li>If <var>value</var> is a newline (U+00A0), take the <span>action</span> for <span>the <code title>insertParagraph</code> command</span> and abort these steps.-- <p class=XXX>WebKit also does magic for tabs, wrapping them in a- whitespace-preserving span.+ <!-- TODO: WebKit also does magic for tabs, wrapping them in a+ whitespace-preserving span. Should we? --> <li>Let <var>node</var> and <var>offset</var> be the <span>active range</span>'s [[startnode]] and [[bpoffset]].@@ -6754,10 +6755,6 @@ <li>If <var>node</var> has only one [[child]], which is a <span>collapsed line break</span>, remove its [[child]] from it.- <p class=XXX>This is wrong in all sorts of cases, like- "foo&lt;b>[]&lt;/b>bar". As above, this is hard to get right without heavy- CSS involvement.- <li>Let <var>text</var> be the result of calling <code data-anolis-spec=domcore title=dom-Document-createTextNode>createTextNode(<var>value</var>)</code> on