[whatwg] Placeholder option for text input boxes

João Eiras joao.eiras at gmail.com
Wed Oct 1 06:32:42 PDT 2008


> This usage is deprecated because it can not be generalized to all possible attribute names
> We recommend the use of generic methods on the core Element interface for setting, getting and removing attributes.

Although I understand your reasoning, I disagree. The DOM does not
exist only to wrap the representation of the original document markup.
The DOM is a programming API and programmings API should make programs
more easy to code nd more performant. Having a get/setAttribute
indirection plus type conversions between serialized strings and back
to a usable type (number, function) are not friendly at all.
The idea of dom properties for attributes is not to find a generic
structure for all atributes, but to have support for known attributes
with known behavior.

Please, don't make such claim again, they are misleading, and clearly
not realistic.





On Wed, Oct 1, 2008 at 12:39 PM, Kristof Zelechovski
<giecrilj at stegny.2a.pl> wrote:
> The attributes are exposed as properties for compatibility with DOM Level 0.
> This usage is deprecated because it can not be generalized to all possible
> attribute names, as is required both for XML and potentially for future
> versions of HTML. We recommend the use of generic methods on the core
> Element interface for setting, getting and removing attributes.
> <http://www.w3.org/TR/2000/WD-DOM-Level-1-20000929/level-one-html.html#ID-64
> 2250288>
>
> -----Original Message-----
> From: Benjamin Hawkes-Lewis [mailto:bhawkeslewis at googlemail.com]
> Sent: Wednesday, October 01, 2008 12:42 PM
> To: Kristof Zelechovski
> Cc: 'Garrett Smith'; whatwg at whatwg.org
> Subject: Re: [whatwg] Placeholder option for text input boxes
>
> Kristof Zelechovski wrote:
>> DOM properties are not becoming obsolete; accessing attributes by
> properties
>> is.
>
> Hmm. Citation?
>
> --
> Benjamin Hawkes-Lewis
>
>



More information about the whatwg mailing list