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

[Bug 24652] New: Deal with associated Realms

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 Feb 2014 12:07:07 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24652-3890@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24652

            Bug ID: 24652
           Summary: Deal with associated Realms
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
          Assignee: cam@mcc.id.au
          Reporter: annevk@annevk.nl
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-script-coord@w3.org
            Blocks: 24318

The realm of an object with a constructor is clear. It's the interface object's
global object's realm.

There should be some way to indicate that if you get window.document, the
Document object returned has the same realm as window. And some way to override
that, consider <iframe>. (Maybe it should be a default with an explicit opt-out
for complicated cases?)

Similarly, for document.createElement() the new Element object will have the
same realm as document.


The complicated case that remains is objects passed to callbacks and events I
suppose. Hopefully bug 24403 helps with that?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 13 February 2014 12:07:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:51 UTC