W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2010

[whatwg] a element and .text

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 21 Jun 2010 14:32:32 -0700
Message-ID: <AANLkTinKs5fZhfEmgsYDJcNJm9tfv7gccfWpgE-G46Pq@mail.gmail.com>
On Mon, Jun 21, 2010 at 12:00 PM, Olli Pettay <Olli.Pettay at helsinki.fi> wrote:
> On 6/21/10 9:25 PM, Jonas Sicking wrote:
>>
>> On Mon, Jun 21, 2010 at 11:09 AM, Olli Pettay<Olli.Pettay at helsinki.fi>
>> ?wrote:
>>>
>>> Hi all,
>>>
>>> I wonder why a element should have .text which
>>> is basically just the same thing as
>>> .textContent.
>>>
>>> I'd prefer removing .text.
>>
>> It's actually worse, see
>>
>>
>> http://mxr.mozilla.org/mozilla-central/source/content/html/content/src/nsHTMLAnchorElement.cpp#367
>>
>> Yes, I'd strongly prefer to remove that too. I say lets remove it from
>> gecko and see if it breaks any sites.
>>
>> / Jonas
>>
>
> I was referring to html5 draft, which specifies that .text
> should be the same as .textContent.
> But sure, the reason why gecko has .text is backwards compatibility
> with Netscape 4. Netscape 4 .text isn't the same as .textContent.

Indeed, my point was that I think we should just go ahead and make the
change in Firefox and we can use information from that test as basis
for changing the spec.

/ Jonas
Received on Monday, 21 June 2010 14:32:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:24 UTC