fixup drop location and workerlocation

Author: mikewest

source

@@ -97016,21 +97016,6 @@ interface <dfn interface>Location</dfn> { // but see also <a href="#the-location
   <code>Document</code></span> is non-null, and <code>about:blank</code> otherwise.</p>
   </div>
 
-  <div algorithm>
-  <p>An element implementing the <code>Location</code> interface has the following <span>extract an
-  origin</span> steps:</p>
-
-  <ol>
-   <li><p>If <span>this</span>'s <span>relevant <code>Document</code></span> is non-null and its
-   <span data-x="concept-document-origin">origin</span> is not <span>same origin-domain</span> with
-   the <span>entry settings object</span>'s
-   <span data-x="concept-settings-object-origin">origin</span>, then return null.</p></li>
-
-   <li><p>Return <span>this</span>'s <span data-x="concept-location-url">url</span>'s
-   <span data-x="concept-url-origin">origin</span>.</p></li>
-  </ol>
-  </div>
-
   <div algorithm>
   <p>A <code>Location</code> object has an associated <dfn
   data-x="concept-location-ancestor-origins-list">ancestor origins list</dfn>. When a
@@ -131804,13 +131789,6 @@ interface <dfn interface>WorkerLocation</dfn> {
 
   <div w-nodev>
 
-  <div algorithm>
-  <p>Objects implementing the <code>WorkerLocation</code> interface's <span>extract an origin</span>
-  steps are to return <span>this</span>'s <span
-  data-x="concept-WorkerLocation-WorkerGlobalScope"><code>WorkerGlobalScope</code> object</span>'s
-  <span data-x="concept-WorkerGlobalScope-url">url</span>'s <span
-  data-x="concept-url-origin">origin</span>.</p>
-  </div>
 
   <p>A <code>WorkerLocation</code> object has an associated <dfn
   data-x="concept-WorkerLocation-WorkerGlobalScope"><code>WorkerGlobalScope</code> object</dfn> (a