Re: [whatwg] a element and .text

2010-08-09 Thread Ian Hickson
On Mon, 21 Jun 2010, Olli Pettay wrote:
 
 I wonder why a element should have .text which
 is basically just the same thing as
 .textContent.
 
 I'd prefer removing .text.

I'm happy to remove it if we can for compat.


On Mon, 21 Jun 2010, Jonas Sicking wrote:
 
 I say lets remove it from gecko and see if it breaks any sites.

Any news on this?


On Mon, 21 Jun 2010, Olli Pettay wrote:
 
 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.

Is it different enough that we should change the spec for compat?

-- 
Ian Hickson   U+1047E)\._.,--,'``.fL
http://ln.hixie.ch/   U+263A/,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'


Re: [whatwg] a element and .text

2010-06-21 Thread Jonas Sicking
On Mon, Jun 21, 2010 at 11:09 AM, Olli Pettay olli.pet...@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


Re: [whatwg] a element and .text

2010-06-21 Thread Olli Pettay

On 6/21/10 9:25 PM, Jonas Sicking wrote:

On Mon, Jun 21, 2010 at 11:09 AM, Olli Pettayolli.pet...@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.


-Olli


Re: [whatwg] a element and .text

2010-06-21 Thread Jonas Sicking
On Mon, Jun 21, 2010 at 12:00 PM, Olli Pettay olli.pet...@helsinki.fi wrote:
 On 6/21/10 9:25 PM, Jonas Sicking wrote:

 On Mon, Jun 21, 2010 at 11:09 AM, Olli Pettayolli.pet...@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