W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2004

[whatwg] DOM support

From: Ian Hickson <ian@hixie.ch>
Date: Wed, 7 Jul 2004 15:20:04 +0000 (UTC)
Message-ID: <Pine.LNX.4.58.0407071519080.24332@dhalsim.dreamhost.com>
On Tue, 6 Jul 2004, Will Levine wrote:
>
> The spec says:
> "Implementations that do not support scripting (or which have their
> scripting features disabled) are exempt from supporting the events and
> DOM interfaces mentioned in this specification."
> However, things like the list attribute and the form attribute are
> defined by DOM functions like getElementById . How does this work?
> Should you just add something saying that if the DOM is not supported,
> the determination of the proper element is implementation-specific?

Good point. It now says:

# Implementations that do not support scripting (or which have their
# scripting features disabled) are exempt from supporting the events and
# DOM interfaces mentioned in this specification. For the parts of this
# specification that are defined in terms of an events model or in terms
# of the DOM, such user agents must still act as if events and the DOM
# were supported.

Is that better?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 7 July 2004 08:20:04 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:35 UTC