This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The latest published version of the DOM4 draft[1] makes the following contradictory statements: 1. "DOM defines a platform-neutral model for events and node trees" 2. "If options' attributeFilter is present and options' attributes is false, throw a JavaScript TypeError" How on earth is specifying JavaScript TypeErrors in the normative text of the specification "platform-neutral"? There are half a dozen or so more references to "JavaScript TypeError" in that draft.
[1]: www.w3.org/TR/dom
JavaScript is a language, not a platform. I don't see the problem.
Indeed.