W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2008

[whatwg] Use cases for Node.getElementById

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Wed, 10 Dec 2008 09:17:40 -0800
Message-ID: <c9e12660812100917k419ab30dh78c237aad189e315@mail.gmail.com>
On Wed, Dec 10, 2008 at 8:10 AM, Calogero Alex Baldacchino
<alex.baldacchino at email.it> wrote:
> Garrett Smith ha scritto:
>>
>> On Sat, Dec 6, 2008 at 7:09 PM, Calogero Alex Baldacchino
>> <alex.baldacchino at email.it> wrote:
>>
>>>
>>> Simon Pieters ha scritto:
>>>
>>>>
>>>> On Fri, 05 Dec 2008 19:19:04 +0100, Calogero Alex Baldacchino
>>>> <alex.baldacchino at email.it> wrote:
>>>>
>>>>
>>>>>
>>>>> [...]
>>>>>
>>>>
>>>> (I'm currently the editor of that proposal, currently located at
>>>> http://simon.html5.org/specs/web-dom-core )
>>>>
>>>>
>>>
>>> I'm reading it :-)
>>>
>>> And I have a few questions.
>>>
>>
>> I did not see a proposal for Element.getElementById.
>>
>> I would not care about that much.
>>
>> I woud rather have
>>
>> Element.getElementsByName.
>>
>> It is perfectly valid for a doucment to have multiple elements w/the
>> same name (though not generally a good idea). I've seen this before.
>>
>> Was this proposed?
>>
>> Garrett
>>
>
> I don't remember what spec exactly stated this first, but I remind of a
> previous HTML version declaring the 'name' attribute as unique in the
> 'global scope' (or something like that),

What?

> meaning the whole document; then, I
> remember 'name' was deprecated in favour of 'id'.

Name is not deprecated. It is, as I said, "perfectly valid". How else
are you going to submit form values?

Garrett
Received on Wednesday, 10 December 2008 09:17:40 UTC

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