13910 2011-08-26 00:11:41 +0000 There can never be no active range 2011-10-04 18:59:42 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - HTML Editing APIs unspecified PC All RESOLVED WORKSFORME P2 normal --- 1 ian ayg ehsan mike public-webapps sideshowbarker+html-editing-api oldest_to_newest 55829 0 ian 2011-08-26 00:11:41 +0000 According to DOM Range, there's always a selection; if it's empty, it is just one range with start=end. This means there's always an active range, so the Editing spec doesn't need to say it can be null. 55890 1 ehsan 2011-08-26 18:23:14 +0000 What if Selection.removeAllRanges is called? 55929 2 ayg 2011-08-28 15:43:41 +0000 According to DOM Range, there's always a selection, but it might have zero ranges. getSelection().getRangeAt(0) will then throw INDEX_SIZE_ERR. In that case, there will be no active range. This is how browsers all behave -- the selection in a new document will have no ranges in it. And the selection must have no ranges in it after removeAllRanges() is called, as Ehsan points out. Is there any specific text in DOM Range that led you to think otherwise? If so, I'll fix it.