On 10/15/14, 1:10 PM, Adam Klein wrote:
Sorry for my delay in responding. Can you say what is simplest for Gecko in this case?
We're still deciding that, but probably something like this: since in Gecko every Promise is associated with a global from the point when it's created (this is the global whose Promise.prototype is used as the proto), we can hang off each Window the list of Promises for that window, and then when we decide the Window is no longer active we'd just mark all those promises as inactive as well, so they will not invoke any callbacks.
One of the reasons I didn't respond to the thread immediately is that from my perspective Chromium has fairly ill-defined behavior for navigated-away pages
Sure. Other browsers do as well.
due to the fact that they often die due to factors that can't be explained by the platform (e.g., their host process dies
That's not observable, really. The observable case is when someone is still holding references to objects in the navigated-away-from page and manipulating them, and in your case that would mean the process is very much alive.
Note that there are actually two somewhat interesting cases here: a page being navigated away from, and the browsing context the page is in being torn down entirely. Thing location.href set on an iframe for the former case, and the <iframe> being removed from the DOM for the latter case.
In my ideal world, the two cases would behave identically, of course.
Also, for case (1), is this all happening within one frame, or is this a cross-frame example?
The latter is more interesting to me personally, since I think it's the harder problem.
-Boris _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
