On Apr 29, 2012, at 1:41 PM, David Young <[email protected]> wrote: > On Sun, Apr 29, 2012 at 10:38:26AM +0300, Aryeh Gregor wrote: >> On Sun, Apr 29, 2012 at 10:29 AM, Ryosuke Niwa <[email protected]> wrote: >>> That sounds like a tangential issue. We can easily extend execCommand to >>> support arbitrary range(s) since such a feature is also valuable in richly >>> editable areas. >> >> Ranges don't exist in plaintext areas. How would you get a Range >> object that selects text in a textarea? That's why we have separate >> .selectionStart, .selectionEnd, etc. properties to start with. > > When you say that ranges do not exist in plaintext areas (not quite sure > what plaintext means in this context), is that for some reason, or is it > just a historical artifact?
Aryeh is referring to the DOM Range interface, which can only apply to nodes that are directly in the DOM, and offsets into their text. The text contents of an <input> or <textarea> are not properly in the DOM, so you cannot use a DOM Range to reference such ranges. I am no sure this is what Ryosuke had in mind though; I think he just meant that in general we could support some notion of a range, and presumably we could come up with one that applies to contentEditable/designMode as well as to text controls. One extreme possibility is to simply change the definition of Range to allow it to address the contents of text input controls. Regards, Maciej
