W3C home > Mailing lists > Public > public-html@w3.org > August 2011

Re: RFC from implementers on Element.innerText

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 02 Aug 2011 19:02:47 +0200
To: "Maciej Stachowiak" <mjs@apple.com>, "Aryeh Gregor" <ayg@aryeh.name>
Cc: "Boris Zbarsky" <bzbarsky@mit.edu>, public-html@w3.org
Message-ID: <op.vzliyxkx64w2qv@annevk-macbookpro.local>
On Tue, 02 Aug 2011 18:52:56 +0200, Aryeh Gregor <ayg@aryeh.name> wrote:
> On Tue, Aug 2, 2011 at 2:48 AM, Maciej Stachowiak <mjs@apple.com> wrote:
>> I guess my preference order would be:
>> 1) If Selection.toString() and Element.innerText can be the same (or  
>> very nearly the same with perhaps a simple flag controlling a few  
>> necessary differences), that would be the best solution to spec.
> I would agree with this if we had a Selection.toString() spec that was
> usable and that browsers were willing to converge on.  However, we
> don't, and it doesn't look like we'll have one in the near future, so
> this isn't practical for the time being.

Why the rush? If Selection.toString() can wait, so can innerText, no?

Anne van Kesteren
Received on Tuesday, 2 August 2011 17:03:23 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:16 UTC