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

[Bug 12295] Make `node instanceof otherWindow.Node` evaluate to false

From: <bugzilla@jessica.w3.org>
Date: Wed, 25 May 2011 04:57:56 +0000
To: public-script-coord@w3.org
Message-Id: <E1QP6AO-0001gf-GW@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12295

--- Comment #5 from Cameron McCormack <cam@mcc.id.au> 2011-05-25 04:57:56 UTC ---
(In reply to comment #4)
> (Also added wording dotted around the spec to define which global environment
> each DOM object is associated with, and which global environment exceptions get
> associated with when they are created and thrown.)

That's not strictly true.  I defined that each "host object implementing an
interface" (term to be renamed when resolving bug 12320) has an associated
global environment, but that it is up to specifications using Web IDL to define
interfaces to state which global environment that is.  This association is what
defines which [[Prototype]] is used for the object.

I would like to avoid requiring every Web IDL using specification from doing
this, but I couldn't think of a way.

If we were still using the AbstractView interface, then in the spec that
defined that I'd say:

  The Document object at AbstractView::document and all of the Nodes created as
  part of that Document (that is, that have ownerDocument set to that Document)
  are associated with the ECMAScript global object on which AbstractView is
  implemented.

Or something.

Still, it's unsatisfying making other specifications include some
ECMAScript-specific text like this.

-- 
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, 25 May 2011 04:57:58 UTC

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