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

Re: RFC from implementers on Element.innerText

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 01 Aug 2011 18:35:04 -0700
Cc: Aryeh Gregor <ayg@aryeh.name>, Edward O'Connor <eoconnor@apple.com>, Adrian Bateman <adrianba@microsoft.com>, Anne van Kesteren <annevk@opera.com>, public-html@w3.org
Message-id: <B2FDC94A-1580-4D5A-AB07-3D6AEE7EFFDF@apple.com>
To: Boris Zbarsky <bzbarsky@MIT.EDU>

On Aug 1, 2011, at 3:01 PM, Boris Zbarsky wrote:

> On 8/1/11 4:20 PM, Maciej Stachowiak wrote:
>> Personal opinion: if the options are to make innerText different from any other text conversion, vs make it identical to Selection.toString()
> 
> It's not clear whether the latter is in fact an option; that depends on how Selection.toString gets specified and whether UAs are willing to do the same for innerText as they do for Selection.toString....
> 
> So far the only proposal I've seen for Selection.toString is "do what the copy operation does", which is neither well-defined nor acceptable for innerText.  In my opinion.

If innerText fundamentally has to behave differently from Selection.toString then making it as simple as possible while maintaining reasonable Web compat seems like a decent option. I don't know whether this is true or not.

Regards,
Maciej
Received on Tuesday, 2 August 2011 01:36:29 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:26 UTC