Jonas Sicking wrote:
Jean-Yves Bitterlich wrote:
A few alternatives were proposed here, referred below as
(i) 'attribute NodeList childElements',
(ii) 'Node item(index)' and
(iii) xpath .querySelector.
I personally like (iii) because it is powerful (or is it just queries
that are
Hello public-webapi,
This is some feedback based on the current draft of DOM Level 3 Events
that I got from the team dealing with events etc at Opera:
* Current spec doesn't take the current situation into account so it
creates just yet another system that implementors have to implement.
-Bindings-20080410/
Latest Version:
http://www.w3.org/TR/DOM-Bindings/
Regards,
Jules
On 11/04/2008, Ian Hickson [EMAIL PROTECTED] wrote:
It would be nice for the spec to explicitly say how to handle argument
calls that have not enough arguments, both for normal methods and for
overloaded methods. (The right answer probably being whatever IE does.)
ECMA-262 3ed has this to
Hello!
I think this algorithm as written is severely broken. The reason is
that [[HasProperty]] will travel the entire chain for each of the
interfaces in order. As such, if a member was to be present on both
Object.prototype and B.prototype in the example IDL, because
A.[[Prototype]] is
There are two use cases for interface flattening that I think it would be
useful for the Web IDL spec to address.
Some interfaces are huge and are defined in various places, but should
look, to authors, as if they were one coherent interface. For example, the
Window object has bits added to
