W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Object sharing across globals

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 18 Jul 2013 16:30:56 -0700
Message-ID: <CADnb78hHoctB5LZ7HY3R1=E0Hz57PYifVnLU6VU=1Z0-YxY9gg@mail.gmail.com>
To: "public-script-coord@w3.org" <public-script-coord@w3.org>
In DOM we already have a problem with [[Prototype]] when a Node moves
to a different global:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20567 (Solutions
welcome in the bug or separate thread.)

I'm wondering what the right solution is for notifications. Say we
have two same-origin globals that can reach other (A & B). Now each of
these creates a Notification object (AN & BN). Now we create a new
method that returns the notifications associated with a given origin.

If we invoke this method in A, what's the expected result? AN & BN
(object equality)? AN & BN' (new object for the one from B)? AN' & BN'
(new objects for everyone).

Now repeat this question for A & B as same-origin, but they cannot
reach other (synchronously, anyway).

The objects have a close() method to make the notification disappear
at which point an event will fire on the objects.

See http://notifications.spec.whatwg.org/ for context.

Received on Thursday, 18 July 2013 23:31:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:17 UTC