On 7/7/16 6:33 AM, Anne van Kesteren wrote:
On Fri, May 20, 2016 at 4:56 PM, Boris Zbarsky <bzbar...@mit.edu> wrote:
2) Create the loadgroup when we're starting the document request. The
channel would just keep it alive while it's active; if we end up creating a
document, the document can grab it from the channel and store it. This
might just work out OK. It will require a bit more up-front work to handle
onload correctly.
How does this approach work for <embed> or <object> where we fetch
first (presumably as part of the parent group) and then decide whether
it becomes its own thing the moment we have all HTTP headers?
The way it works right now is that the <embed> or <object> load is part
of the loadgroup for the parent document until we decide it's creating a
child browsing context (docshell). At that point we create the child
browsing context and move the load into the loadgroup associated with
that browsing context.
So in the new world, we'd keep doing the same, but in addition to
creating the child docshell and its loadgroup at the point when we
detect that we need a child browsing context we would also create the
child document loadgroup and move the embed/object load into _that_.
-Boris
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
