Script Origin Tracking: Difference between revisions

Script Origin Tracking (view source)

687 bytes removed , 13 May 2011

Simplify browserContext markup origins: just refer to the window.

Confirmed users

497

edits

@@ Line 85: / Line 85: @@
 <dl>
-<dt><code>{ browsingContext:<i>url</i> }</code>
+<dt><code>{ browsingContext:<i>window</i> }</code>
-<dd>This describes a top-level browsing context visiting <i>url</i>. <i>Url</i> is an absolute URL, a string.
+<dd>This describes a top-level browsing context whose window is <i>window</i>, a DOM window object. From the window you can find the URL being visited, and the parent browsing context, if any.
-<dt><code>{ browsingContext:<i>url</i>, container:<i>container</i>, markupLocation:<i>location</i> }</code>
-<dd>As above, except that the context is a nested browsing context whose browsing context container is <i>container</i> (an <code>&lt;iframe&gt;</code> element, perhaps) appearing in markup at <i>location</i>.
-<dt><code>{ browsingContext:<i>url</i>, container:<i>container</i>, scriptLocation:<i>location</i> }</code>
-<dd>As above, except that the browsing context container's URL was set by JavaScript at <i>location</i>. This is also the form used for
-<dt><code>{ browsingContext:<i>url</i>, opener:<i>opener</i> }</code>
-<dd>This describes an auxiliary browsing context whose opener browsing context is <i>opener</i>. <i>Opener</i> is a markup origin value.
 <dt><code>{ dynamicMarkup:<i>node</i>, method:<i>method</i>, scriptLocation:<i>location</i> }</code>