W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2011

[Bug 12320] ECMAScript binding forbids using ECMAScript to implement many interfaces.

From: <bugzilla@jessica.w3.org>
Date: Wed, 16 Mar 2011 20:33:41 +0000
To: public-script-coord@w3.org
Message-Id: <E1PzxPZ-0001Di-0L@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12320

--- Comment #2 from Allen Wirfs-Brock <allen@wirfs-brock.com> 2011-03-16 20:33:40 UTC ---
(In reply to comment #1)
Then you need to specify the actual requirements rather than hiding them behind
some broad prohibitive on using a specific implementation language.

For example for appendChild you might say that the argument Node must be an
object that was created as if by called some list of specified methods that
would include createElement and others. 

Or you might define a categorization of object such as "trusted DOM object"
that means something over and beyond just implemented a certain interface.  You
when then require that certain arguments in addition to implementing some
interface must also be trusted DOM objects.

It is them up to the implementers to enforce those requirements, regardless of
their implementation language of choice.

When the time comes to start implementing parts of the DOM in JavaScript (and
that time is near) the current prohibition isn't going to stop implementors
from doing it.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 16 March 2011 20:33:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:03 UTC