- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Aug 2015 10:31:37 +0000
- To: public-media-capture-logs@w3.org
@alvestrand the lifetime is defined by HTML. Global objects are typically 1:1 with documents. You can assume as much for the purposes of your API. Here's defined what happens when a document is unloaded: https://html.spec.whatwg.org/multipage/browsers.html#unload-a-document Which is triggered by navigation. Navigation also takes care of creating new global objects and such. What you typically do in specification land if you want to rely on the lifetime of some other object is saying that the other object has an associated _X_. Now you can rely on that _X_ being there as long as the other object is around. And fiddle with it. Then if you need to do cleanup steps yourself for your own objects, you write those down, and attach them to https://html.spec.whatwg.org/multipage/browsers.html#unloading-document-cleanup-steps. I'm hoping that in due course objects being associated with some other object can become a bit more formal in terms of "internal slots" and some other stuff, but we aren't so organized just yet. -- GitHub Notif of comment by annevk See https://github.com/w3c/mediacapture-main/issues/222#issuecomment-132967834
Received on Thursday, 20 August 2015 10:31:39 UTC