- From: Philippe Le Hegaret <plh@w3.org>
- Date: Thu, 08 Jan 2004 18:36:25 -0500
- To: Curt Arnold <carnold@houston.rr.com>
- Cc: WWW DOM <www-dom@w3.org>
On my way to a question related to the default error handler, I found
that one:
> http://www.w3.org/TR/DOM-Level-3-Core/core.html#TypeInfo
>
> Because parameters are exposed as properties in the ECMAScript
> Language Binding, names are recommended to follow the section "5.16
> Identifiers" of [Unicode] with the addition of the character '-'
> (HYPHEN-MINUS) but it is not enforced by the DOM implementation.
>
> The configuration parameters do not appear to be exposed as properties
> in the ECMAScript language binding. If they were, allowing
> hyphen-minus would probably cause significant issues.
See the note in the ECMAScript binding:
[[
Note: In addition of having DOMConfiguration parameters exposed to the
application using the setParameter and getParameter, those parameters
are also exposed as ECMAScript properties on the DOMConfiguration
object. The name of the parameter is converted into a property name
using a camel-case convention: the character '-' (HYPHEN-MINUS) is
removed and the following character is being replaced by its uppercase
equivalent.
]]
http://www.w3.org/TR/2003/CR-DOM-Level-3-Core-20031107/ecma-script-binding.html
> DOM Level 3 Core Implementations are required to recognize all
> parameters defined in this specification.
>
> Many of the parameters are XML specific. The current DOM spec
> preserves the distinction between Fundamental and Extended interfaces
> leaving the possibility for a L3 Core conformant implementation for
> HTML or another markup language. Possibly the list could be split
> into parameters supported by all implementations and parameters that
> are required to be supported by implementations that return true for
> hasFeature("XML", "3.0")
It is indeed a good point...
Philippe
Received on Thursday, 8 January 2004 18:36:27 UTC