On Thu, 13 Jan 2011, Aryeh Gregor wrote:
The HTMLCollection interface does specify supported property indices,
but then also specifies behavior for out-of-bounds values which seems to
conflict with WebIDL (returns null instead of throwing). Same for
DOMStringList, DOMTokenList, and
On Thu, 13 Jan 2011 22:05:54 +0100, Aryeh Gregor
simetrical+...@gmail.com wrote:
There are a bunch of places where it says When invoked with the same
argument the same NodeList object may be returned as returned by an
earlier call. Shouldn't this be either required or prohibited in any
given
On 01/13/2011 10:05 PM, Aryeh Gregor wrote:
In defining the interface for Node, some of the attributes are defined
like The parentElement attribute must return the parent node of the
context node if there is a parent and it is an Element node, or null
otherwise. while others are defined like
On Fri, Jan 14, 2011 at 11:41 PM, James Graham jgra...@opera.com wrote:
On 01/13/2011 10:05 PM, Aryeh Gregor wrote:
There are a bunch of places where it says When invoked with the same
argument the same NodeList object may be returned as returned by an
earlier call. Shouldn't this be
On 1/14/11 5:53 AM, Robert O'Callahan wrote:
... except I guess it can, because it could set expando properties on the
old NodeList and check for their presence later. Sigh.
We could make expandos on nodelists pin them so they can't be collected
as long as they can be reached via DOM APIs;
Various IDLs in the spec use [NoNull], but apparently WebIDL no longer
defines that (the Changes section says it was removed in 2008). I'm
not sure exactly what it used to do, but the spec should be updated to
use whatever WebIDL now defines as a replacement.
In defining the interface for Node,
