W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2000

Re: Is document.<formName>.<fieldName>.value DOM-1 compliant

From: Glenn Adams <gadams@vgi.com>
Date: Wed, 8 Nov 2000 21:24:12 -0500
Message-ID: <003301c049f4$26fac370$47070001@vgi.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: <www-dom@w3.org>
Actually, I do have "a DOM-0 spec" as it were. I wrote it into the Advanced
Television Systems Committee (ATSC) DASE (DTV Application Software Environment)
Declarative Applications (DA) specification. This spec precisely specifies
"DOM-0" legacy behavior as was expressed by a union of IE3 and NN3
functionality, roughly what one can describe as JavaScript 1.1. The material is
partly based on a new SMPTE standard underway to codify DOM-0 behavior for use
with ATVEF (Advanced Television Enhancement Forum) content.

While I would agree that the behavior being discussed is is not explicitly
supported in DOM-[12] or by Java bindings, it is universally supported by all
UAs that accommodate this well establish client-side JavaScript usage.
Notwithstanding this, if one is creating content for DOM-[12] and beyond, I
would recommend using DOM-[12] core functionality and not this technique.


----- Original Message -----
From: "David Brownell" <david-b@pacbell.net>
To: "Glenn Adams" <gadams@vgi.com>; <Tami.K.Decker@supervalu.com>;
Sent: Wednesday, November 08, 2000 5:58 PM
Subject: Re: Is document.<formName>.<fieldName>.value DOM-1 compliant

> > What you are referring to is valid DOM-0 (legacy) functionality
> Hmm, do you have a DOM-0 spec that shows that it's
> not just some implementation-specific thingie?  :-)
> To my recollection, no spec for a "DOM-0" exists.
> I think it's EXTREMELY unwise to rely on anything
> that can only claim to be a legacy.  Use DOM L1
> functionality wherever possible.
> - Dave
Received on Wednesday, 8 November 2000 21:24:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:07 UTC