From 07facabd80b72f42cd2544029081c59f0c84c38a Mon Sep 17 00:00:00 2001
From: Domenic Denicola <d@domenic.me>
Date: Wed, 26 May 2021 16:06:58 -0400
Subject: [PATCH] Specify window.clientInformation

Closes #2379.
---
 source | 29 +++++++++++++++++------------
 1 file changed, 17 insertions(+), 12 deletions(-)

diff --git a/source b/source
index fa6bcc221fa..e63c690e122 100644
--- a/source
+++ b/source
@@ -80102,7 +80102,8 @@ interface <dfn interface>Window</dfn> : <span>EventTarget</span> {
   // Indexed access is taken care of by the <span>WindowProxy</span> exotic object.
 
   // the user agent
-  readonly attribute <span>Navigator</span> <span data-x="dom-navigator">navigator</span>; <!-- IE also has window.clientInformation === window.navigator -->
+  readonly attribute <span>Navigator</span> <span data-x="dom-navigator">navigator</span>;
+  readonly attribute <span>Navigator</span> <span data-x="dom-clientInformation">clientInformation</span>; // legacy alias of .navigator
   readonly attribute boolean <span data-x="dom-originAgentCluster">originAgentCluster</span>;
 
   // user prompts
@@ -95432,14 +95433,9 @@ function sendData(data) {
 
   <h4>The <code>Navigator</code> object</h4>
 
-  <div w-nodev>
-
-  <p>The <dfn attribute for="Window"><code data-x="dom-navigator">navigator</code></dfn> attribute
-  of the <code>Window</code> interface must return an instance of the <code>Navigator</code>
-  interface, which represents the identity and state of the user agent (the client), and allows web
-  pages to register themselves as potential protocol handlers:</p>
-
-  </div>
+  <p>Instances of <code>Navigator</code> represent the identity and state of the user agent (the
+  client). They also serve as a generic global under which various APIs are located in this and
+  other specifications.</p>
 
   <pre><code class="idl">[Exposed=Window]
 interface <dfn interface>Navigator</dfn> {
@@ -95455,8 +95451,17 @@ interface <dfn interface>Navigator</dfn> {
 
   <div w-nodev>
 
-  <p>These interface mixins are defined separately so that <code>WorkerNavigator</code> can re-use
-  parts of the <code>Navigator</code> interface.</p>
+  <p class="note">These interface mixins are defined separately so that <code>WorkerNavigator</code> can reuse parts of
+  the <code>Navigator</code> interface.</p>
+
+  <p>Each <code>Window</code> has an <dfn>associated <code>Navigator</code></dfn>, which is a <code>Navigator</code>
+  object. Upon creation of the <code>Window</code> object, its <span>associated <code>Navigator</code></span> must be
+  set to a <span>new</span> <code>Navigator</code> object created in the <code>Window</code> object's <span
+  data-x="concept-relevant-realm">relevant Realm</span>.</p>
+
+  <p>The <dfn attribute for="Window"><code data-x="dom-navigator">navigator</code></dfn> and <dfn attribute
+  for="Window"><code data-x="dom-clientInformation">clientInformation</code></dfn> getter steps are to return
+  <span>this</span>'s <span>associated <code>Navigator</code></span>.
 
   </div>
 
@@ -95487,7 +95492,7 @@ interface <dfn interface>Navigator</dfn> {
   mode</dfn>, which is either <i>Chrome</i>, <i>Gecko</i>, or <i>WebKit</i>.</p>
 
   <p class="note">The <span data-x="concept-navigator-compatibility-mode">navigator compatibility
-  mode</span> constrains the <span>NavigatorID</span> interface to the combinations of attribute
+  mode</span> constrains the <code>NavigatorID</code> mixin to the combinations of attribute
   values and presence of <code data-x="dom-navigator-taintEnabled">taintEnabled()</code> and <code
   data-x="dom-navigator-oscpu">oscpu</code> that are known to be compatible with existing web
   content.</p>