- From: <bugzilla@jessica.w3.org>
- Date: Fri, 17 Jan 2014 11:51:53 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24318
Bug ID: 24318
Summary: Define the Realm of objects
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: DOM
Assignee: annevk@annevk.nl
Reporter: annevk@annevk.nl
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, www-dom@w3.org
Selective quote from Boris
http://lists.w3.org/Archives/Public/www-tag/2014Jan/0112.html below:
> Here's what WebIDL says:
>
> Every platform object is associated with a global environment, just
> as the initial objects are. It is the responsibility of
> specifications using Web IDL to state which global environment
> (or, by proxy, which global object) each platform object is
> associated with.
>
> Here's an example not involving promises that's currently underspecified, I
> believe:
>
> window1.document.createElement.call(window2.document, "span");
>
> I've put the relevant testcase at
> http://web.mit.edu/bzbarsky/www/testcases/multiple-realms/createElement-1.html
> if you want to take a look. Browsers consistently create the element in the
> realm of window2 in this case, but the DOM spec doesn't seem to actually
> define the behavior right now, unless I'm totally missing something. It
> should do so, for example by defining that an element is associated with the
> global environment of its owner document and then defining the global
> environment for documents as needed. DOMParser and XMLHttpRequest make that
> last bit slightly exciting.
I guess I'll file follow up bugs once I fix this in DOM.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 17 January 2014 11:51:54 UTC