Point out that the "first range" stuff is nonsense
authorAryeh Gregor <AryehGregor+gitcommit@gmail.com>
Thu, 12 May 2011 12:04:42 -0600
changeset 106 1afdd066499b
parent 105 66971eac8be7
child 107 7b65be873827
Point out that the "first range" stuff is nonsense

Also thanks to feedback by Tim Down, same thread:
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2011-May/031537.html
editcommands.html
source.html
--- a/editcommands.html	Thu May 12 11:58:52 2011 -0600
+++ b/editcommands.html	Thu May 12 12:04:42 2011 -0600
@@ -1507,6 +1507,13 @@
 <p class=XXX>Querying the value or state of an unrecognized command throws an
 exception in IE and Firefox.  Need to consider changing to that behavior.
 
+<p class=XXX>I say "first range" because I think that's what Gecko actually
+does, and Gecko is the only one that allows multiple ranges in a selection.
+This is keeping in mind that it stores ranges sorted by start, not by the order
+the user added them, and silently removes or shortens existing ranges to avoid
+overlap.  It probably makes the most sense in the long term to have the command
+affect all ranges.  But I'll leave this for later.
+
 <p>The possible values for <var title="">commandId</var>, and their corresponding
 meanings, are as follows.  These values must be compared to the argument in an
 <a class=external data-anolis-spec=domcore href=http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#ascii-case-insensitive>ASCII case-insensitive</a> manner.  The
--- a/source.html	Thu May 12 11:58:52 2011 -0600
+++ b/source.html	Thu May 12 12:04:42 2011 -0600
@@ -1527,6 +1527,13 @@
 <p class=XXX>Querying the value or state of an unrecognized command throws an
 exception in IE and Firefox.  Need to consider changing to that behavior.
 
+<p class=XXX>I say "first range" because I think that's what Gecko actually
+does, and Gecko is the only one that allows multiple ranges in a selection.
+This is keeping in mind that it stores ranges sorted by start, not by the order
+the user added them, and silently removes or shortens existing ranges to avoid
+overlap.  It probably makes the most sense in the long term to have the command
+affect all ranges.  But I'll leave this for later.
+
 <p>The possible values for <var>commandId</var>, and their corresponding
 meanings, are as follows.  These values must be compared to the argument in an
 <span data-anolis-spec=domcore>ASCII case-insensitive</span> manner.  The