From 50ce162039321f0d29b20c57bd9e4c2625028b35 Mon Sep 17 00:00:00 2001 From: Mike West Date: Mon, 7 Oct 2019 09:30:24 +0200 Subject: [PATCH] Change nested navigations' fetches destinations. Currently, top-level and nested navigations set a request destination of "document" when performing the "process a navigate fetch" algorithm. This patch follows whatwg/fetch#948, splitting "document" into "frame" and "iframe" for nested navigation requests. --- source | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/source b/source index 1376405d014..0ec130e32dd 100644 --- a/source +++ b/source @@ -31087,7 +31087,8 @@ interface HTMLEmbedElement : HTMLElement { document's relevant settings object, destination is "embed", credentials mode is "include", and whose use-URL-credentials flag is set.

+ data-x="">include", mode is "navigate", and whose use-URL-credentials flag is set.

  • Fetch request.

    @@ -31573,7 +31574,8 @@ interface HTMLObjectElement : HTMLElement { document's relevant settings object, destination is "object", credentials mode is "include", and whose use-URL-credentials flag is set.

  • + data-x="">include", mode is "navigate", and whose use-URL-credentials flag is set.

  • @@ -84511,10 +84513,21 @@ interface Location { // but see also id.

  • -
  • If browsingContext's container is non-null - and has a browsing context scope origin, then set request's origin to that browsing context scope - origin.

  • +
  • +

    If browsingContext's container is non-null:

    + +
      +
    1. If the browsingContext's container has a + browsing context scope origin, then set request's origin to that browsing context scope + origin.

    2. + +
    3. Set request's destination to browsingContext's + container's local + name.

    4. +
    +
  • Let reservedEnvironment be null.