1. 7.3 文書シーケンスのインフラ
      1. 7.3.1 ナビゲート可能
        1. 7.3.1.1 横断可能なナビゲート可能
        2. 7.3.1.2 Top-level traversables
        3. 7.3.1.3 Child navigables
        4. 7.3.1.4 Jake diagrams
        5. 7.3.1.5 Related navigable collections
        6. 7.3.1.6 Navigable destruction
        7. 7.3.1.7 ナビゲート可能なターゲット名
      2. 7.3.2 ブラウジングコンテキスト
        1. 7.3.2.1 Creating browsing contexts
        2. 7.3.2.2 Related browsing contexts
        3. 7.3.2.3 Groupings of browsing contexts
      3. 7.3.3 完全にアクティブな文書

7.3 文書シーケンスのインフラ

この標準は、文書シーケンスをグループ化するためのいくつかの関連する概念を含む。簡潔で非規範的な要約として：

この標準の大部分はナビゲート可能の言語で動作するが、特定のAPIはブラウジングコンテキストスイッチの存在を公開するため、標準の一部はブラウジングコンテキストの観点から動作する必要がある。

ナビゲート可能は、アクティブなセッション履歴エントリーを介して、Documentをユーザーに提示する。各ナビゲート可能は、以下を持つ：

現在のセッション履歴エントリーとアクティブなセッション履歴エントリーは通常同じであるが、次の場合には同期しなくなる。

ナビゲート可能のアクティブ文書は、そのアクティブなセッション履歴エントリーの文書である。

これは、ナビゲート可能の最上位のトラバース可能のセッション履歴トラバースキュー内から安全に読み取ることができる。ナビゲート可能のアクティブな履歴エントリーは同期的に変更できるが、新しいエントリーは常に同じDocumentが含まれる。

ナビゲート可能のアクティブなブラウジングコンテキストは、そのアクティブな文書のブラウジングコンテキストである。このナビゲート可能が横断可能なナビゲート可能である場合、そのアクティブなブラウジングコンテキストはトップレベルのブラウジングコンテキストになる。

ナビゲート可能のアクティブなWindowProxyは、そのアクティブなブラウジングコンテキストの関連付けられたWindowProxyである。

ナビゲート可能のアクティブなウィンドウは、そのアクティブなWindowProxyの[[Window]]である。

これは常に、ナビゲート可能のアクティブな文書の関連するグローバルオブジェクトと等しくなる。これは、アクティブにするアルゴリズムによって同期が保たれる。

ナビゲート可能のターゲット名は、そのアクティブなセッション履歴エントリーの文書状態のナビゲート可能ターゲット名である。

To get the node navigable of a node node, return the navigable whose active document is node's node document, or null if there is no such navigable.

To initialize the navigable navigable navigable, given a document state documentState and an optional navigable-or-null parent (default null):

  1. Assert: documentState's document is non-null.

  2. Let entry be a new session history entry, with

    URL
    documentState's document's URL
    document state
    documentState

    The caller of this algorithm is responsible for initializing entry's step; it will be left as "pending" until that is complete.

  3. Set navigable's current session history entry to entry.

  4. Set navigable's active session history entry to entry.

  5. Set navigable's parent to parent.

7.3.1.1 横断可能なナビゲート可能

横断可能なナビゲート可能はナビゲート可能であり、それ自身およびその子孫ナビゲート可能に対して、どのセッション履歴エントリーが現在のセッション履歴エントリーおよびアクティブなセッション履歴エントリーであるべきかを制御する。

ナビゲート可能のプロパティに加えて、横断可能なナビゲート可能は次を持つ：

To get the traversable navigable of a navigable inputNavigable:

  1. Let navigable be inputNavigable.

  2. While navigable is not a traversable navigable, set navigable to navigable's parent.

  3. Return navigable.

7.3.1.2 Top-level traversables

A top-level traversable is a traversable navigable with a null parent.

Currently, all traversable navigables are top-level traversables. Future proposals envision introducing non-top-level traversables.

A user agent holds a top-level traversable set (a set of top-level traversables). These are typically presented to the user in the form of browser windows or browser tabs.

To get the top-level traversable of a navigable inputNavigable:

  1. Let navigable be inputNavigable.

  2. While navigable's parent is not null, set navigable to navigable's parent.

  3. Return navigable.

To create a new top-level traversable given a browsing context-or-null opener and a string targetName:

  1. Let document be null.

  2. If opener is null, then set document to the second return value of creating a new top-level browsing context and document.

  3. Otherwise, set document to the second return value of creating a new auxiliary browsing context and document given opener.

  4. Let documentState be a new document state, with

    document
    document
    initiator origin
    null if opener is null; otherwise, document's origin
    origin
    document's origin
    navigable target name
    targetName
    about base URL
    document's about base URL

  5. Let traversable be a new traversable navigable.

  6. Initialize the navigable traversable given documentState.

  7. Let initialHistoryEntry be traversable's active session history entry.

  8. Set initialHistoryEntry's step to 0.

  9. Append initialHistoryEntry to traversable's session history entries.

  10. If opener is non-null, then legacy-clone a traversable storage shed given opener's top-level traversable and traversable. [STORAGE]

  11. Append traversable to the user agent's top-level traversable set.

  12. Return traversable.

To create a fresh top-level traversable given a URL initialNavigationURL and an optional POST resource-or-null initialNavigationPostResource (default null):

  1. Let traversable be the result of creating a new top-level traversable given null and the empty string.

  2. Navigate traversable to initialNavigationURL using traversable's active document, with documentResource set to initialNavigationPostResource.

    We treat these initial navigations as traversable navigating itself, which will ensure all relevant security checks pass.

  3. Return traversable.

7.3.1.3 Child navigables

Certain elements (for example, iframe elements) can present a navigable to the user. These elements are called navigable containers.

Each navigable container has a content navigable, which is either a navigable or null. 最初はnullである。

The container of a navigable navigable is the navigable container whose content navigable is navigable, or null if there is no such element.

The container document of a navigable navigable is the result of running these steps:

  1. If navigable's container is null, then return null.

  2. Return navigable's container's node document.

    This is equal to navigable's container's shadow-including root as navigable's container has to be connected.

The container document of a Document document is the result of running these steps:

  1. If document's node navigable is null, then return null.

  2. Return document's node navigable's container document.

A navigable navigable is a child navigable of another navigable potentialParent when navigable's parent is potentialParent. We can also just say that a navigable "is a child navigable", which means that its parent is non-null.

All child navigables are the content navigable of their container.

The content document of a navigable container container is the result of running these steps:

  1. If container's content navigable is null, then return null.

  2. Let document be container's content navigable's active document.

  3. documentの生成元およびcontainerのノード文書の生成元が同一生成元ドメインでない場合、nullを返す。

  4. documentを返す。

The content window of a navigable container container is the result of running these steps:

  1. If container's content navigable is null, then return null.

  2. Return container's content navigable's active WindowProxy's object.

To create a new child navigable, given an element element:

  1. Let parentNavigable be element's node navigable.

  2. Let group be element's node document's browsing context's top-level browsing context's group.

  3. Let browsingContext and document be the result of creating a new browsing context and document given element's node document, element, and group.

  4. Let targetName be null.

  5. If element has a name content attribute, then set targetName to the value of that attribute.

  6. Let documentState be a new document state, with

    document
    document
    initiator origin
    document's origin
    origin
    document's origin
    navigable target name
    targetName
    about base URL
    document's about base URL

  7. Let navigable be a new navigable.

  8. Initialize the navigable navigable given documentState and parentNavigable.

  9. Set element's content navigable to navigable.

  10. Let historyEntry be navigable's active session history entry.

  11. Let traversable be parentNavigable's traversable navigable.

  12. Append the following session history traversal steps to traversable:

    1. Let parentDocState be parentNavigable's active session history entry's document state.

    2. Let parentNavigableEntries be the result of getting session history entries for parentNavigable.

    3. Let targetStepSHE be the first session history entry in parentNavigableEntries whose document state equals parentDocState.

    4. Set historyEntry's step to targetStepSHE's step.

    5. Let nestedHistory be a new nested history whose id is navigable's id and entries list is « historyEntry ».

    6. Append nestedHistory to parentDocState's nested histories.

    7. Update for navigable creation/destruction given traversable.

7.3.1.4 Jake diagrams

A useful method for visualizing sequences of documents, and in particular navigables and their session history entries, is the Jake diagram. A typical Jake diagram is the following:

01234
top/t-a/t-a#foo/t-b
frames[0]/i-0-a/i-0-b
frames[1]/i-1-a/i-1-b

Here, each numbered column denotes a possible value for the traversable's session history step. Each labeled row depicts a navigable, as it transitions between different URLs and documents. The first, labeled top, being the top-level traversable, and the others being child navigables. The documents are given by the background color of each cell, with a new background color indicating a new document in that navigable. The URLs are given by the text content of the cells; usually they are given as relative URLs for brevity, unless a cross-origin case is specifically under investigation. A given navigable might not exist at a given step, in which case the corresponding cells are empty. The bold-italic step number depicts the current session history step of the traversable, and all cells with bold-italic URLs represent the current session history entry for that row's navigable.

Thus, the above Jake diagram depicts the following sequence of events:

  1. A top-level traversable is created, starting a the URL /t-a, with two child navigables starting at /i-0-a and /i-1-a respectively.

  2. The first child navigable is navigated to another document, with URL /i-0-b.

  3. The second child navigable is navigated to another document, with URL /i-1-b.

  4. The top-level traversable is navigated to the same document, updating its URL to /t-a#foo.

  5. The top-level traversable is navigated to another document, with URL /t-b. (Notice how this document, of course, does not carry over the old document's child navigables.)

  6. The traversable was traversed by a delta of −3, back to step 1.

Jake diagrams are a powerful tool for visualizing the interactions of multiple navigables, navigations, and traversals. They cannot capture every possible interaction — for example, they only work with a single level of nesting — but we will have ocassion to use them to illustrate several complex situations throughout this standard.

Jake diagrams are named after their creator, the inimitable Jake Archibald.

It is often helpful in this standard's algorithms to look at collections of navigables starting at a given Document. This section contains a curated set of algorithms for collecting those navigables.

The return values of these algorithms are ordered so that parents appears before their children. Callers rely on this ordering.

Starting with a Document, rather than a navigable, is generally better because it makes the caller cognizant of whether they are starting with a fully active Document or not. Although non-fully active Documents do have ancestor and descendant navigables, they often behave as if they don't (e.g., in the window.parent getter).

The ancestor navigables of a Document document are given by these steps:

  1. Let navigable be document's node navigable's parent.

  2. Let ancestors be an empty list.

  3. While navigable is not null:

    1. Prepend navigable to ancestors.

    2. Set navigable to navigable's parent.

  4. Return ancestors.

The inclusive ancestor navigables of a Document document are given by these steps:

  1. Let navigables be document's ancestor navigables.

  2. Append document's node navigable to navigables.

  3. Return navigables.

The descendant navigables of a Document document are given by these steps:

  1. Let navigables be new list.

  2. Let navigableContainers be a list of all shadow-including descendants of document that are navigable containers, in shadow-including tree order.

  3. For each navigableContainer of navigableContainers:

    1. If navigableContainer's content navigable is null, then continue.

    2. Extend navigables with navigableContainer's content navigable's active document's inclusive descendant navigables.

  4. Return navigables.

The inclusive descendant navigables of a Document document are given by these steps:

  1. Let navigables be « document's node navigable ».

  2. Extend navigables with document's descendant navigables.

  3. Return navigables.

These descendant-collecting algorithms are described as looking at the DOM tree of descendant Document objects. In reality, this is often not feasible since the DOM tree can be in another process from the caller of the algorithm. Instead, implementations generally replicate the appropriate trees across processes.

The document-tree child navigables of a Document document are given by these steps:

  1. If document's node navigable is null, then return the empty list.

  2. Let navigables be new list.

  3. Let navigableContainers be a list of all descendants of document that are navigable containers, in tree order.

  4. For each navigableContainer of navigableContainers:

    1. If navigableContainer's content navigable is null, then continue.

    2. Append navigableContainer's content navigable to navigables.

  5. Return navigables.

7.3.1.6 Navigable destruction

To destroy a child navigable given a navigable container container:

  1. Let navigable be container's content navigable.

  2. If navigable is null, then return.

  3. Set container's content navigable to null.

  4. Inform the navigation API about child navigable destruction given navigable.

  5. Destroy a document and its descendants given navigable's active document.

  6. Let parentDocState be container's node navigable's active session history entry's document state.

  7. Remove the nested history from parentDocState's nested histories whose id equals navigable's id.

  8. Let traversable be container's node navigable's traversable navigable.

  9. Append the following session history traversal steps to traversable:

    1. Update for navigable creation/destruction given traversable.

To destroy a top-level traversable given a top-level traversable traversable:

  1. Let browsingContext be traversable's active browsing context.

  2. For each historyEntry in traversable's session history entries in what order?:

    1. Let document be historyEntry's document.

    2. If document is not null, then destroy a document and its descendants given document.

  3. Remove browsingContext.

  4. Remove traversable from the user interface (e.g., close or hide its tab in a tabbed browser).

  5. Remove traversable from the user agent's top-level traversable set.

User agents may destroy a top-level traversable at any time (typically, in response to user requests).

To close a top-level traversable traversable:

  1. If traversable's is closing is true, then return.

  2. Let toUnload be traversable's active document's inclusive descendant navigables.

  3. If the result of checking if unloading is canceled for toUnload is true, then return.

  4. Append the following session history traversal steps to traversable:

    1. Let afterAllUnloads be an algorithm step which destroys traversable.

    2. Unload a document and its descendants given traversable's active document, null, and afterAllUnloads.

ナビゲート可能は、ターゲット名を指定できる。これは、特定のAPI（window.open()、a要素のtarget属性など）が、そのナビゲート可能でナビゲーションを目標にできるようにする文字列である。

A valid navigable target name is any string with at least one character that does not contain both an ASCII tab or newline and a U+003C (<), and it does not start with a U+005F (_). (Names starting with a U+005F (_) are reserved for special keywords.)

妥当なナビゲート可能名またはキーワードは、妥当なナビゲート可能なターゲット名またはASCII大文字・小文字不区別で_blank、_self、_parent、または_topの1つに一致するいずれかとなる任意の文字列である。

これらの値は、以下の（非規範的な）テーブルで要約されるように、ページがサンドボックス化されるかどうかに基づいて異なる意味を持つ。この表において、"current"はリンクまたはスクリプト内にあるナビゲート可能を意味し、"parent"はリンクまたはスクリプト内にあるナビゲート可能の親を意味し、"top"はリンクまたはスクリプトにあるナビゲート可能のトップレベルのトラバース可能を意味し、"new"は、nullの親をもつ新しいトラバース可能を意味し（これはさまざまなユーザー設定とユーザーエージェントポリシーに従って、補助ブラウジングコンテキストを使用できる）、"none"は何も起こらないことを意味し、"maybe new"は"、"allow-popups"キーワードがsandbox属性でも指定される場合（またはユーザーがサンドボックスを上書きした場合）に"new"と同じであり、そうでなければ"none"と同じである。

キーワード普通の効果iframeでの効果
sandbox=""sandbox="allow-top-navigation"
リンクおよびフォーム送信に対して、何も指定しないcurrentcurrentcurrent
空文字列currentcurrentcurrent
_blanknewmaybe newmaybe new
_selfcurrentcurrentcurrent
親が存在しない場合の_parentcurrentcurrentcurrent
親がまたトップである場合の_parentparent/topnoneparent/top
存在するがトップでない場合の_parentparentnonenone
トップが現在である場合の_topcurrentcurrentcurrent
トップが現在でない場合の_toptopnonetop
名前が存在しないnewmaybe newmaybe new
名前が存在しかつ子孫であるspecified descendantspecified descendantspecified descendant
名前が存在し現在であるcurrentcurrentcurrent
名前が存在しかつトップとなる祖先であるspecified ancestornonespecified ancestor/top
名前が存在しかつトップでない祖先であるspecified ancestornonenone
他の名前が共通のトップとともに存在するspecifiednonenone
familiarかつある許可されたサンドボックス化されたナビゲーターである場合、異なるトップをもつ名前が存在するspecifiedspecifiedspecified
familiarだがある許可されたサンドボックス化されたナビゲーターでない場合、異なるトップをもつ名前が存在するspecifiednonenone
familiarでない、異なるトップをもつ名前が存在するnewmaybe newmaybe new

サンドボックス化されたブラウジングコンテキストの制限のほとんどは、他のアルゴリズムにより適用される。たとえば、下記で与えられるナビゲート可能を選択するための規則でなく、ナビゲーションアルゴリズムとして。

The rules for choosing a navigable, given a string name, a navigable currentNavigable, and a boolean noopener are as follows:

  1. Let chosen be null.

  2. Let windowType be "existing or none".

  3. Let sandboxingFlagSet be currentNavigable's active document's active sandboxing flag set.

  4. If name is the empty string or an ASCII case-insensitive match for "_self", then set chosen to currentNavigable.

  5. Otherwise, if name is an ASCII case-insensitive match for "_parent", set chosen to currentNavigable's parent, if any, and currentNavigable otherwise.

  6. Otherwise, if name is an ASCII case-insensitive match for "_top", set chosen to currentNavigable's traversable navigable.

  7. Otherwise, if name is not an ASCII case-insensitive match for "_blank", there exists a navigable whose target name is the same as name, currentNavigable's active browsing context is familiar with that navigable's active browsing context, and the user agent determines that the two browsing contexts are related enough that it is ok if they reach each other, set chosen to that navigable. If there are multiple matching navigables, the user agent should pick one in some arbitrary consistent manner, such as the most recently opened, most recently focused, or more closely related, and set chosen to it.

    This will be made more precise in issue #313.

  8. Otherwise, a new top-level traversable is being requested, and what happens depends on the user agent's configuration and abilities — it is determined by the rules given for the first applicable option from the following list:

    The user agent may inform the user that a popup has been blocked.

    If sandboxingFlagSet has the sandboxed auxiliary navigation browsing context flag set

    The user agent may report to a developer console that a popup has been blocked.

    If the user agent has been configured such that in this instance it will create a new top-level traversable

    1. Set windowType to "new and unrestricted".

    2. Let currentDocument be currentNavigable's active document.

    3. If currentDocument's cross-origin opener policy's value is "same-origin" or "same-origin-plus-COEP", and currentDocument's origin is not same origin with currentDocument's relevant settings object's top-level origin, then:

      1. Set noopener to true.

      2. Set name to "_blank".

      3. Set windowType to "new with no opener".

      In the presence of a cross-origin opener policy, nested documents that are cross-origin with their top-level browsing context's active document always set noopener to true.

    4. Let chosen be null.

    5. Let targetName be the empty string.

    6. If name is not an ASCII case-insensitive match for "_blank", then set targetName to name.

    7. If noopener is true, then set chosen to the result of creating a new top-level traversable given null and targetName.

    8. Otherwise:

      1. Set chosen to the result of creating a new top-level traversable given currentNavigable's active browsing context and targetName.

      2. If sandboxingFlagSet's sandboxed navigation browsing context flag is set, then set chosen's active browsing context's one permitted sandboxed navigator to currentNavigable's active browsing context.

    9. If sandboxingFlagSet's sandbox propagates to auxiliary browsing contexts flag is set, then all the flags that are set in sandboxingFlagSet must be set in chosen's active browsing context's popup sandboxing flag set.

    If the newly created navigable chosen is immediately navigated, then the navigation will be done as a "replace" navigation.

    If the user agent has been configured such that in this instance it will choose currentNavigable

    Set chosen to currentNavigable.

    If the user agent has been configured such that in this instance it will not find a navigable

    Do nothing.

    User agents are encouraged to provide a way for users to configure the user agent to always choose currentNavigable.

  9. Return chosen and windowType.

7.3.2 ブラウジングコンテキスト

ブラウジングコンテキストは、一連の文書をプログラムで表現したものであり、その複数の文書が1つのナビゲート可能を受け入れることができる。各ブラウジングコンテキストは、対応するWindowProxyオブジェクトだけでなく、次のオブジェクトを持つ：

ブラウジングコンテキストのアクティブウィンドウは、その WindowProxyオブジェクトの[[Window]]内部スロット値である。ブラウジングコンテキストのアクティブ文書は、そのアクティブウィンドウに関連付けられたDocumentである。

ブラウジングコンテキストのトップレベルトラバース可能は、そのアクティブ文書のノードナビゲート可能のトップレベルトラバース可能である。

補助がtrueであるブラウジングコンテキストは、補助ブラウジングコンテキストとして知られる。補助ブラウジングコンテキストは常にトップレベルブラウジングコンテキストである。

独立した補助的であるという概念が必要かどうかは定かでない。issue#5680では、オープナーブラウジングコンテキストがnullかどうかを使用することで、これを単純化できる可能性があることが示されている。

近頃の仕様では、ブラウジングコンテキストグループスイッチおよびエージェントクラスタ割り当ての微妙な問題を処理していない限り、ほとんどの場合、ブラウジングコンテキストの概念の使用を避けるべできである。代わりに、Documentおよびナビゲート可能の概念がたいていより適切である。

Documentのブラウジングコンテキストは、ブラウジングコンテキストまたはnullであり。最初はnullである。

Documentは、必ずしも非nullのブラウジングコンテキストを持つとは限らない。具体的には、データマイニングツールはブラウジングコンテキストをインスタンス化できないだろう。createDocument()のような API を使用して作成されたDocumentは、非nullのブラウジングコンテキストを持つことはない。また、iframe要素に対してもともと作成されたDocument、これは文書から削除されるが、そのブラウジングコンテキストはnull outであるため、関連付けられたブラウジングコンテキストを持たない。

一般に、Documentオブジェクトが非nullブラウジングコンテキストを持っている限り、WindowオブジェクトからDocumentオブジェクトへのマッピングは1対1になる。例外が1つある。Windowは、マッピングが1対2になるように、同じブラウジングコンテキストで2番目のDocumentのプレゼンテーションに再利用できる。これは、ブラウジングコンテキストが、最初のabout:blank Documentから別の文書にナビゲートされたときに発生する。これは置換で行われる。

7.3.2.1 Creating browsing contexts

To create a new browsing context and document, given null or a Document object creator, null or an element embedder, and a browsing context group group:

  1. Let browsingContext be a new browsing context.

  2. Let unsafeContextCreationTime be the unsafe shared current time.

  3. Let creatorOrigin be null.

  4. Let creatorBaseURL be null.

  5. If creator is non-null, then:

    1. Set creatorOrigin to creator's origin.

    2. Set creatorBaseURL to creator's document base URL.

    3. Set browsingContext's virtual browsing context group ID to creator's browsing context's top-level browsing context's virtual browsing context group ID.

  6. Let sandboxFlags be the result of determining the creation sandboxing flags given browsingContext and embedder.

  7. Let origin be the result of determining the origin given about:blank, sandboxFlags, and creatorOrigin.

  8. Let permissionsPolicy be the result of creating a permissions policy given embedder and origin. [PERMISSIONSPOLICY]

  9. Let agent be the result of obtaining a similar-origin window agent given origin, group, and false.

  10. Let realm execution context be the result of creating a new realm given agent and the following customizations:

  11. Let topLevelCreationURL be about:blank if embedder is null; otherwise embedder's relevant settings object's top-level creation URL.

  12. Let topLevelOrigin be origin if embedder is null; otherwise embedder's relevant settings object's top-level origin.

  13. Set up a window environment settings object with about:blank, realm execution context, null, topLevelCreationURL, and topLevelOrigin.

  14. Let loadTimingInfo be a new document load timing info with its navigation start time set to the result of calling coarsen time with unsafeContextCreationTime and the new environment settings object's cross-origin isolated capability.

  15. Let document be a new Document, with:

    type
    "html"
    content type
    "text/html"
    mode
    "quirks"
    origin
    origin
    browsing context
    browsingContext
    permissions policy
    permissionsPolicy
    active sandboxing flag set
    sandboxFlags
    load timing info
    loadTimingInfo
    is initial about:blank
    true
    about base URL
    creatorBaseURL
    allow declarative shadow roots
    true

  16. If creator is non-null, then:

    1. Set document's referrer to the serialization of creator's URL.

    2. Set document's policy container to a clone of creator's policy container.

    3. If creator's origin is same origin with creator's relevant settings object's top-level origin, then set document's cross-origin opener policy to creator's browsing context's top-level browsing context's active document's cross-origin opener policy.

  17. Assert: document's URL and document's relevant settings object's creation URL are about:blank.

  18. Mark document as ready for post-load tasks.

  19. Populate with html/head/body given document.

  20. Make active document.

  21. Completely finish loading document.

  22. Return browsingContext and document.

To create a new top-level browsing context and document:

  1. Let group and document be the result of creating a new browsing context group and document.

  2. Return group's browsing context set[0] and document.

To create a new auxiliary browsing context and document, given a browsing context opener:

  1. Let openerTopLevelBrowsingContext be opener's top-level traversable's active browsing context.

  2. Let group be openerTopLevelBrowsingContext's group.

  3. Assert: group is non-null, as navigating invokes this directly.

  4. Set browsingContext and document be the result of creating a new browsing context and document with opener's active document, null, and group.

  5. Set browsingContext's is auxiliary to true.

  6. Append browsingContext to group.

  7. Set browsingContext's opener browsing context to opener.

  8. Set browsingContext's virtual browsing context group ID to openerTopLevelBrowsingContext's virtual browsing context group ID.

  9. Set browsingContext's opener origin at creation to opener's active document's origin.

  10. Return browsingContext and document.

To determine the origin, given a URL url, a sandboxing flag set sandboxFlags, and an origin-or-null sourceOrigin:

  1. If sandboxFlags has its sandboxed origin browsing context flag set, then return a new opaque origin.

  2. If url is null, then return a new opaque origin.

  3. If url is about:srcdoc, then:

    1. Assert: sourceOrigin is non-null.

    2. Return sourceOrigin.

  4. If url matches about:blank and sourceOrigin is non-null, then return sourceOrigin.

  5. Return url's origin.

The cases that return sourceOrigin result in two Documents that end up with the same underlying origin, meaning that document.domain affects both.

7.3.2.2 Related browsing contexts

A browsing context potentialDescendant is said to be an ancestor of a browsing context potentialAncestor if the following algorithm returns true:

  1. Let potentialDescendantDocument be potentialDescendant's active document.

  2. If potentialDescendantDocument is not fully active, then return false.

  3. Let ancestorBCs be the list obtained by taking the browsing context of the active document of each member of potentialDescendantDocument's ancestor navigables.

  4. If ancestorBCs contains potentialAncestor, then return true.

  5. falseを返す。

A top-level browsing context is a browsing context whose active document's node navigable is a traversable navigable.

It is not required to be a top-level traversable.

The top-level browsing context of a browsing context start is the result of the following algorithm:

  1. If start's active document is not fully active, then return null.

  2. Let navigable be start's active document's node navigable.

  3. While navigable's parent is not null, set navigable to navigable's parent.

  4. Return navigable's active browsing context.

A browsing context A is familiar with a second browsing context B if the following algorithm returns true:

  1. If A's active document's origin is same origin with B's active document's origin, then return true.

  2. If A's top-level browsing context is B, then return true.

  3. If B is an auxiliary browsing context and A is familiar with B's opener browsing context, then return true.

  4. If there exists an ancestor browsing context of B whose active document has the same origin as the active document of A, then return true.

    This includes the case where A is an ancestor browsing context of B.

  5. falseを返す。

7.3.2.3 Groupings of browsing contexts

A top-level browsing context has an associated group (null or a browsing context group). 最初はnullである。

A user agent holds a browsing context group set (a set of browsing context groups).

A browsing context group holds a browsing context set (a set of top-level browsing contexts).

A top-level browsing context is added to the group when the group is created. All subsequent top-level browsing contexts added to the group will be auxiliary browsing contexts.

A browsing context group has an associated agent cluster map (a weak map of agent cluster keys to agent clusters). User agents are responsible for collecting agent clusters when it is deemed that nothing can access them anymore.

A browsing context group has an associated historical agent cluster key map, which is a map of origins to agent cluster keys. This map is used to ensure the consistency of the origin-keyed agent clusters feature by recording what agent cluster keys were previously used for a given origin.

The historical agent cluster key map only ever gains entries over the lifetime of the browsing context group.

A browsing context group has a cross-origin isolation mode, which is a cross-origin isolation mode. It is initially "none".

A cross-origin isolation mode is one of three possible values: "none", "logical", or "concrete".

"logical" and "concrete" are similar. They are both used for browsing context groups where:

On some platforms, it is difficult to provide the security properties required to grant safe access to the APIs gated by the cross-origin isolated capability. As a result, only "concrete" can grant access that capability. "logical" is used on platform not supporting this capability, where various restrictions imposed by cross-origin isolation will still apply, but the capability is not granted.

To create a new browsing context group and document:

  1. Let group be a new browsing context group.

  2. Append group to the user agent's browsing context group set.

  3. Let browsingContext and document be the result of creating a new browsing context and document with null, null, and group.

  4. Append browsingContext to group.

  5. Return group and document.

To append a top-level browsing context browsingContext to a browsing context group group:

  1. Append browsingContext to group's browsing context set.

  2. Set browsingContext's group to group.

To remove a top-level browsing context browsingContext:

  1. Assert: browsingContext's group is non-null.

  2. Let group be browsingContext's group.

  3. Set browsingContext's group to null.

  4. Remove browsingContext from group's browsing context set.

  5. If group's browsing context set is empty, then remove group from the user agent's browsing context group set.

Append and remove are primitive operations that help define the lifetime of a browsing context group. They are called by higher-level creation and destruction operations for Documents and browsing contexts.

When there are no Document objects whose browsing context equals a given browsing context (i.e., all such Documents have been destroyed), and that browsing context's WindowProxy is eligible for garbage collection, then the browsing context will never be accessed again. If it is a top-level browsing context, then at this point the user agent must remove it.

7.3.3 完全にアクティブな文書

dがナビゲート可能navigableのアクティブな文書であり、navigableが最上位のトラバース可能であるか、navigableのコンテナー文書が完全にアクティブである場合、Document dは完全にアクティブであるといわれる。

これらは要素に関連付けられているため、子ナビゲート可能は常に、親ナビゲート可能内の特定のDocument（コンテナー文書）に関連付けられている。ユーザーエージェントは、コンテナー文書自体が完全にアクティブではない子ナビゲート可能とユーザーが対話することを許可してはならない。

次の例は、Documentが、完全にアクティブではない一方で、ノードナビゲート可能のアクティブな文書になる方法を示す。ここで、a.htmlはブラウザーのウィンドウに読み込まれ、b-1.htmlは示されているように最初にiframeに読み込まれ、b-2.htmlおよびc.htmlは省略される（単に空の文書にすることができる）。

<!-- a.html -->
<!DOCTYPE html>
<html lang="en">
<title>Navigable A</title>

<iframe src="b-1.html"></iframe>
<button onclick="frames[0].location.href = 'b-2.html'">Click me</button>

<!-- b-1.html -->
<!DOCTYPE html>
<html lang="en">
<title>Navigable B</title>

<iframe src="c.html"></iframe>

この時点で、a.html、b-1.html、およびc.htmlによって提供される文書はすべて、それぞれのノードナビゲート可能のアクティブな文書である。それらはまた、すべて完全にアクティブである。

buttonをクリックし、b-2.htmlからナビゲート可能Bに新しいDocumentをロードする後に、次の結果が得られる：