[html5] r3351 - [giow] (2) Try to specify the occasional reuse of Window objects when navigating [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Jul 1 15:08:23 PDT 2009
Author: ianh
Date: 2009-07-01 15:08:21 -0700 (Wed, 01 Jul 2009)
New Revision: 3351
Modified:
index
source
Log:
[giow] (2) Try to specify the occasional reuse of Window objects when navigating away from about:blank initial docs to docs in the same origin. (credit: bz, sw)
Modified: index
===================================================================
--- index 2009-07-01 21:38:46 UTC (rev 3350)
+++ index 2009-07-01 22:08:21 UTC (rev 3351)
@@ -45380,19 +45380,29 @@
<div class=impl>
- <p>The <code title="">defaultView</code> attribute on the
- <code>Document</code> object's <code>DocumentView</code> interface
- must return the <a href=#browsing-context>browsing context</a>'s
- <code><a href=#windowproxy>WindowProxy</a></code> object, not the actual
+ <p>The <code title=dom-document-defaultView>defaultView</code>
+ attribute on the <code>Document</code> object's
+ <code>DocumentView</code> interface must return the <a href=#browsing-context>browsing
+ context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object, not the actual
<code>AbstractView</code> object of the <a href=#default-view>default
view</a>. <a href=#refsDOM3VIEWS>[DOM3VIEWS]</a></p>
</div>
- <p class=note>The <code title="">document</code> attribute of an
- <code>AbstractView</code> object representing a <a href=#view>view</a>
- gives the view's corresponding <code>Document</code> object. <a href=#refsDOM2VIEWS>[DOM2VIEWS]</a></p>
+ <p class=note>The <code title=dom-document>document</code>
+ attribute of an <code>AbstractView</code> object representing a
+ <a href=#view>view</a> gives the view's corresponding
+ <code>Document</code> object. <a href=#refsDOM2VIEWS>[DOM2VIEWS]</a></p>
+ <p class=note>In general, there is a 1-to-1 mapping from the
+ <code><a href=#window>Window</a></code> object to the <code>Document</code> object. In
+ one particular case, a set of <a href=#view title=view>views</a> can be
+ reused for the presentation of a second <code>Document</code> in the
+ same <a href=#browsing-context>browsing context</a>, such that the mapping is then
+ 2:1. This occurs when a <a href=#browsing-context>browsing context</a> is <a href=#navigate title=navigate>navigated</a> from the initial
+ <code><a href=#about:blank>about:blank</a></code> <code>Document</code> to another, with
+ <a href=#replacement-enabled>replacement enabled</a>.</p>
+
<div class=impl>
<p>Events that use the <code>UIEvent</code> interface are related to
@@ -46279,8 +46289,10 @@
<p class=note>The <a href=#browsing-context>browsing context</a>'s <a href=#default-view>default
view</a>'s <code><a href=#window>Window</a></code> object <a href=#implied-strong-reference title="implied strong
- reference">has a strong reference of its own</a> to its
- <code>Document</code> object.</p>
+ reference">has a strong reference</a> to its
+ <code>Document</code> object through the <code title=dom-document>document</code> attribute of the
+ <code>AbstractView</code> interface. Thus, references from other
+ scripts to either of those objects will keep both alive. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
<p class=note>Whenever a <code>Document</code> object is <a href=#discard-a-document title="discard a Document">discarded</a>, it is also removed from
the list of <span>the worker's <code>Document</code>s</span> of each
@@ -51757,6 +51769,22 @@
is set when <a href=#concept-js-deref title=concept-js-deref>dereferencing a
<code>javascript:</code> URL</a>.</p>
+ <p><dfn id=create-a-document-object title="create a Document object">Creating a new
+ <code>Document</code> object</dfn>: When a <code>Document</code>
+ is created as part of the above steps, a new set of <a href=#view title=view>views</a> along with the associated
+ <code><a href=#window>Window</a></code> object must be created and associated with the
+ <code>Document</code>, with one exception: if the <a href=#browsing-context>browsing
+ context</a>'s only entry in its <a href=#session-history>session history</a> is
+ the <code><a href=#about:blank>about:blank</a></code> <code>Document</code> that was added
+ when the <a href=#browsing-context>browsing context</a> was created, and navigation
+ is occurring with <a href=#replacement-enabled>replacement enabled</a>, and that
+ <code>Document</code> has the <a href=#same-origin>same origin</a> as the new
+ <code>Document</code>, then the <code><a href=#window>Window</a></code> object and
+ associated <a href=#view title=view>views</a> of that
+ <code>Document</code> must be used instead, and the <code title=dom-document>document</code> attribute of the
+ <code>AbstractView</code> objects of those <a href=#view title=view>views</a> must be changed to point to the new
+ <code>Document</code> instead.</p>
+
</li>
<li id=navigate-non-Document>
@@ -51862,11 +51890,11 @@
<h4 id=read-html><span class=secno>6.11.2 </span><dfn title=navigate-html>Page load processing model for HTML files</dfn></h4>
<p>When an HTML document is to be loaded in a <a href=#browsing-context>browsing
- context</a>, the user agent must create a <code>Document</code>
- object, mark it as being an <a href=#html-documents title="HTML documents">HTML
- document</a>, create an <a href=#html-parser>HTML parser</a>, associate it
- with the document, and begin to use the bytes provided for the
- document as the <a href=#the-input-stream>input stream</a> for that parser.</p>
+ context</a>, the user agent must <a href=#create-a-document-object>create a
+ <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, create an <a href=#html-parser>HTML
+ parser</a>, associate it with the document, and begin to use the
+ bytes provided for the document as the <a href=#the-input-stream>input stream</a> for
+ that parser.</p>
<p class=note>The <a href=#the-input-stream>input stream</a> converts bytes into
characters for use in the <a href=#tokenization title=tokenization>tokenizer</a>. This process relies, in part,
@@ -51894,9 +51922,9 @@
<h4 id=read-xml><span class=secno>6.11.3 </span><dfn title=navigate-xml>Page load processing model for XML files</dfn></h4>
<p>When faced with displaying an XML file inline, user agents must
- first create a <code>Document</code> object, following the
- requirements of the XML and Namespaces in XML recommendations, RFC
- 3023, DOM3 Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
+ first <a href=#create-a-document-object>create a <code>Document</code> object</a>, following
+ the requirements of the XML and Namespaces in XML recommendations,
+ RFC 3023, DOM3 Core, and other relevant specifications. <a href=#refsXML>[XML]</a> <a href=#refsXMLNS>[XMLNS]</a> <a href=#refsRFC3023>[RFC3023]</a> <a href=#refsDOM3CORE>[DOM3CORE]</a></p>
<p>The actual HTTP headers and other metadata, not the headers as
mutated or implied by the algorithms given in this specification,
@@ -51948,14 +51976,13 @@
<h4 id=read-text><span class=secno>6.11.4 </span><dfn title=navigate-text>Page load processing model for text files</dfn></h4>
<p>When a plain text document is to be loaded in a <a href=#browsing-context>browsing
- context</a>, the user agent should create a <code>Document</code>
- object, mark it as being an <a href=#html-documents title="HTML documents">HTML
- document</a>, create an <a href=#html-parser>HTML parser</a>, associate it
- with the document, act as if the tokenizer had emitted a start tag
- token with the tag name "pre", set the <a href=#tokenization>tokenization</a>
- stage's <a href=#content-model-flag>content model flag</a> to <i>PLAINTEXT</i>, and
- begin to pass the stream of characters in the plain text document to
- that tokenizer.</p>
+ context</a>, the user agent should <a href=#create-a-document-object>create a
+ <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, create an <a href=#html-parser>HTML
+ parser</a>, associate it with the document, act as if the
+ tokenizer had emitted a start tag token with the tag name "pre", set
+ the <a href=#tokenization>tokenization</a> stage's <a href=#content-model-flag>content model
+ flag</a> to <i>PLAINTEXT</i>, and begin to pass the stream of
+ characters in the plain text document to that tokenizer.</p>
<p>The rules for how to convert the bytes of the plain text document
into actual characters are defined in RFC 2046, RFC 2646, and
@@ -51990,14 +52017,13 @@
<h4 id=read-image><span class=secno>6.11.5 </span><dfn title=navigate-image>Page load processing model for images</dfn></h4>
<p>When an image resource is to be loaded in a <a href=#browsing-context>browsing
- context</a>, the user agent should create a <code>Document</code>
- object, mark it as being an <a href=#html-documents title="HTML documents">HTML
- document</a>, append an <code><a href=#the-html-element>html</a></code> element to the
- <code>Document</code>, append a <code><a href=#the-head-element>head</a></code> element and a
- <code><a href=#the-body-element>body</a></code> element to the <code><a href=#the-html-element>html</a></code> element, append
- an <code><a href=#the-img-element>img</a></code> to the <code><a href=#the-body-element>body</a></code> element, and set the
- <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute of the
- <code><a href=#the-img-element>img</a></code> element to the address of the image.</p>
+ context</a>, the user agent should <a href=#create-a-document-object>create a
+ <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, append an
+ <code><a href=#the-html-element>html</a></code> element to the <code>Document</code>, append a
+ <code><a href=#the-head-element>head</a></code> element and a <code><a href=#the-body-element>body</a></code> element to the
+ <code><a href=#the-html-element>html</a></code> element, append an <code><a href=#the-img-element>img</a></code> to the
+ <code><a href=#the-body-element>body</a></code> element, and set the <code title=attr-img-src><a href=#attr-img-src>src</a></code> attribute of the <code><a href=#the-img-element>img</a></code>
+ element to the address of the image.</p>
<!-- next three paragraphs are similar to the navigate-text section,
keep them in sync -->
@@ -52024,12 +52050,12 @@
<p>When a resource that requires an external resource to be rendered
is to be loaded in a <a href=#browsing-context>browsing context</a>, the user agent
- should create a <code>Document</code> object, mark it as being an
- <a href=#html-documents title="HTML documents">HTML document</a>, append an
- <code><a href=#the-html-element>html</a></code> element to the <code>Document</code>, append a
- <code><a href=#the-head-element>head</a></code> element and a <code><a href=#the-body-element>body</a></code> element to the
- <code><a href=#the-html-element>html</a></code> element, append an <code><a href=#the-embed-element>embed</a></code> to the
- <code><a href=#the-body-element>body</a></code> element, and set the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute of the
+ should <a href=#create-a-document-object>create a <code>Document</code> object</a>, mark it
+ as being an <a href=#html-documents title="HTML documents">HTML document</a>,
+ append an <code><a href=#the-html-element>html</a></code> element to the <code>Document</code>,
+ append a <code><a href=#the-head-element>head</a></code> element and a <code><a href=#the-body-element>body</a></code> element
+ to the <code><a href=#the-html-element>html</a></code> element, append an <code><a href=#the-embed-element>embed</a></code> to
+ the <code><a href=#the-body-element>body</a></code> element, and set the <code title=attr-embed-src><a href=#attr-embed-src>src</a></code> attribute of the
<code><a href=#the-embed-element>embed</a></code> element to the address of the resource.</p>
<!-- next three paragraphs are similar to the navigate-text section,
@@ -52060,13 +52086,12 @@
<h4 id=read-ua-inline><span class=secno>6.11.7 </span><dfn title=navigate-ua-inline>Page load processing model for inline content that doesn't have a DOM</dfn></h4>
<p>When the user agent is to display a user agent page inline in a
- <a href=#browsing-context>browsing context</a>, the user agent should create a
- <code>Document</code> object, mark it as being an <a href=#html-documents title="HTML
- documents">HTML document</a>, and then either associate that
- <code>Document</code> with a custom rendering that is not rendered
- using the normal <code>Document</code> rendering rules, or mutate
- that <code>Document</code> until it represents the content the user
- agent wants to render.</p>
+ <a href=#browsing-context>browsing context</a>, the user agent should <a href=#create-a-document-object>create a
+ <code>Document</code> object</a>, mark it as being an <a href=#html-documents title="HTML documents">HTML document</a>, and then either
+ associate that <code>Document</code> with a custom rendering that is
+ not rendered using the normal <code>Document</code> rendering rules,
+ or mutate that <code>Document</code> until it represents the content
+ the user agent wants to render.</p>
<!-- next two paragraphs are similar to the navigate-text section,
keep them in sync -->
@@ -55480,8 +55505,8 @@
<pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : MouseEvent {
readonly attribute <a href=#datatransfer>DataTransfer</a> <a href=#dom-dragevent-datatransfer title=dom-DragEvent-dataTransfer>dataTransfer</a>;
- void <a href=#dom-dragevent-initdragevent title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
- void <a href=#dom-dragevent-initdrageventns title=dom-DragEvent-initDragEventNS>initDragEventNS</a>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in DOMString modifiersListArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
+ void <a href=#dom-dragevent-initdragevent title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in <span>AbstractView</span> viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
+ void <a href=#dom-dragevent-initdrageventns title=dom-DragEvent-initDragEventNS>initDragEventNS</a>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in <span>AbstractView</span> viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in DOMString modifiersListArg, in <a href=#datatransfer>DataTransfer</a> dataTransferArg);
};</pre>
<dl class=domintro><dt><var title="">event</var> . <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code></dt>
Modified: source
===================================================================
--- source 2009-07-01 21:38:46 UTC (rev 3350)
+++ source 2009-07-01 22:08:21 UTC (rev 3351)
@@ -51669,20 +51669,31 @@
<div class="impl">
- <p>The <code title="">defaultView</code> attribute on the
- <code>Document</code> object's <code>DocumentView</code> interface
- must return the <span>browsing context</span>'s
- <code>WindowProxy</code> object, not the actual
+ <p>The <code title="dom-document-defaultView">defaultView</code>
+ attribute on the <code>Document</code> object's
+ <code>DocumentView</code> interface must return the <span>browsing
+ context</span>'s <code>WindowProxy</code> object, not the actual
<code>AbstractView</code> object of the <span>default
view</span>. <a href="#refsDOM3VIEWS">[DOM3VIEWS]</a></p>
</div>
- <p class="note">The <code title="">document</code> attribute of an
- <code>AbstractView</code> object representing a <span>view</span>
- gives the view's corresponding <code>Document</code> object. <a
+ <p class="note">The <code title="dom-document">document</code>
+ attribute of an <code>AbstractView</code> object representing a
+ <span>view</span> gives the view's corresponding
+ <code>Document</code> object. <a
href="#refsDOM2VIEWS">[DOM2VIEWS]</a></p>
+ <p class="note">In general, there is a 1-to-1 mapping from the
+ <code>Window</code> object to the <code>Document</code> object. In
+ one particular case, a set of <span title="view">views</span> can be
+ reused for the presentation of a second <code>Document</code> in the
+ same <span>browsing context</span>, such that the mapping is then
+ 2:1. This occurs when a <span>browsing context</span> is <span
+ title="navigate">navigated</span> from the initial
+ <code>about:blank</code> <code>Document</code> to another, with
+ <span>replacement enabled</span>.</p>
+
<div class="impl">
<p>Events that use the <code>UIEvent</code> interface are related to
@@ -52682,8 +52693,12 @@
<p class="note">The <span>browsing context</span>'s <span>default
view</span>'s <code>Window</code> object <span title="implied strong
- reference">has a strong reference of its own</span> to its
- <code>Document</code> object.</p>
+ reference">has a strong reference</span> to its
+ <code>Document</code> object through the <code
+ title="dom-document">document</code> attribute of the
+ <code>AbstractView</code> interface. Thus, references from other
+ scripts to either of those objects will keep both alive. <a
+ href="#refsDOMVIEWS">[DOMVIEWS]</a></p>
<p class="note">Whenever a <code>Document</code> object is <span
title="discard a Document">discarded</span>, it is also removed from
@@ -59044,6 +59059,25 @@
is set when <span title="concept-js-deref">dereferencing a
<code>javascript:</code> URL</span>.</p>
+ <p><dfn title="create a Document object">Creating a new
+ <code>Document</code> object</dfn>: When a <code>Document</code>
+ is created as part of the above steps, a new set of <span
+ title="view">views</span> along with the associated
+ <code>Window</code> object must be created and associated with the
+ <code>Document</code>, with one exception: if the <span>browsing
+ context</span>'s only entry in its <span>session history</span> is
+ the <code>about:blank</code> <code>Document</code> that was added
+ when the <span>browsing context</span> was created, and navigation
+ is occurring with <span>replacement enabled</span>, and that
+ <code>Document</code> has the <span>same origin</span> as the new
+ <code>Document</code>, then the <code>Window</code> object and
+ associated <span title="view">views</span> of that
+ <code>Document</code> must be used instead, and the <code
+ title="dom-document">document</code> attribute of the
+ <code>AbstractView</code> objects of those <span
+ title="view">views</span> must be changed to point to the new
+ <code>Document</code> instead.</p>
+
</li>
<li id="navigate-non-Document">
@@ -59175,11 +59209,12 @@
<h4 id="read-html"><dfn title="navigate-html">Page load processing model for HTML files</dfn></h4>
<p>When an HTML document is to be loaded in a <span>browsing
- context</span>, the user agent must create a <code>Document</code>
- object, mark it as being an <span title="HTML documents">HTML
- document</span>, create an <span>HTML parser</span>, associate it
- with the document, and begin to use the bytes provided for the
- document as the <span>input stream</span> for that parser.</p>
+ context</span>, the user agent must <span>create a
+ <code>Document</code> object</span>, mark it as being an <span
+ title="HTML documents">HTML document</span>, create an <span>HTML
+ parser</span>, associate it with the document, and begin to use the
+ bytes provided for the document as the <span>input stream</span> for
+ that parser.</p>
<p class="note">The <span>input stream</span> converts bytes into
characters for use in the <span
@@ -59209,9 +59244,9 @@
<h4 id="read-xml"><dfn title="navigate-xml">Page load processing model for XML files</dfn></h4>
<p>When faced with displaying an XML file inline, user agents must
- first create a <code>Document</code> object, following the
- requirements of the XML and Namespaces in XML recommendations, RFC
- 3023, DOM3 Core, and other relevant specifications. <a
+ first <span>create a <code>Document</code> object</span>, following
+ the requirements of the XML and Namespaces in XML recommendations,
+ RFC 3023, DOM3 Core, and other relevant specifications. <a
href="#refsXML">[XML]</a> <a href="#refsXMLNS">[XMLNS]</a> <a
href="#refsRFC3023">[RFC3023]</a> <a
href="#refsDOM3CORE">[DOM3CORE]</a></p>
@@ -59274,14 +59309,14 @@
<h4 id="read-text"><dfn title="navigate-text">Page load processing model for text files</dfn></h4>
<p>When a plain text document is to be loaded in a <span>browsing
- context</span>, the user agent should create a <code>Document</code>
- object, mark it as being an <span title="HTML documents">HTML
- document</span>, create an <span>HTML parser</span>, associate it
- with the document, act as if the tokenizer had emitted a start tag
- token with the tag name "pre", set the <span>tokenization</span>
- stage's <span>content model flag</span> to <i>PLAINTEXT</i>, and
- begin to pass the stream of characters in the plain text document to
- that tokenizer.</p>
+ context</span>, the user agent should <span>create a
+ <code>Document</code> object</span>, mark it as being an <span
+ title="HTML documents">HTML document</span>, create an <span>HTML
+ parser</span>, associate it with the document, act as if the
+ tokenizer had emitted a start tag token with the tag name "pre", set
+ the <span>tokenization</span> stage's <span>content model
+ flag</span> to <i>PLAINTEXT</i>, and begin to pass the stream of
+ characters in the plain text document to that tokenizer.</p>
<p>The rules for how to convert the bytes of the plain text document
into actual characters are defined in RFC 2046, RFC 2646, and
@@ -59318,14 +59353,15 @@
<h4 id="read-image"><dfn title="navigate-image">Page load processing model for images</dfn></h4>
<p>When an image resource is to be loaded in a <span>browsing
- context</span>, the user agent should create a <code>Document</code>
- object, mark it as being an <span title="HTML documents">HTML
- document</span>, append an <code>html</code> element to the
- <code>Document</code>, append a <code>head</code> element and a
- <code>body</code> element to the <code>html</code> element, append
- an <code>img</code> to the <code>body</code> element, and set the
- <code title="attr-img-src">src</code> attribute of the
- <code>img</code> element to the address of the image.</p>
+ context</span>, the user agent should <span>create a
+ <code>Document</code> object</span>, mark it as being an <span
+ title="HTML documents">HTML document</span>, append an
+ <code>html</code> element to the <code>Document</code>, append a
+ <code>head</code> element and a <code>body</code> element to the
+ <code>html</code> element, append an <code>img</code> to the
+ <code>body</code> element, and set the <code
+ title="attr-img-src">src</code> attribute of the <code>img</code>
+ element to the address of the image.</p>
<!-- next three paragraphs are similar to the navigate-text section,
keep them in sync -->
@@ -59352,12 +59388,12 @@
<p>When a resource that requires an external resource to be rendered
is to be loaded in a <span>browsing context</span>, the user agent
- should create a <code>Document</code> object, mark it as being an
- <span title="HTML documents">HTML document</span>, append an
- <code>html</code> element to the <code>Document</code>, append a
- <code>head</code> element and a <code>body</code> element to the
- <code>html</code> element, append an <code>embed</code> to the
- <code>body</code> element, and set the <code
+ should <span>create a <code>Document</code> object</span>, mark it
+ as being an <span title="HTML documents">HTML document</span>,
+ append an <code>html</code> element to the <code>Document</code>,
+ append a <code>head</code> element and a <code>body</code> element
+ to the <code>html</code> element, append an <code>embed</code> to
+ the <code>body</code> element, and set the <code
title="attr-embed-src">src</code> attribute of the
<code>embed</code> element to the address of the resource.</p>
@@ -59390,13 +59426,13 @@
<h4 id="read-ua-inline"><dfn title="navigate-ua-inline">Page load processing model for inline content that doesn't have a DOM</dfn></h4>
<p>When the user agent is to display a user agent page inline in a
- <span>browsing context</span>, the user agent should create a
- <code>Document</code> object, mark it as being an <span title="HTML
- documents">HTML document</span>, and then either associate that
- <code>Document</code> with a custom rendering that is not rendered
- using the normal <code>Document</code> rendering rules, or mutate
- that <code>Document</code> until it represents the content the user
- agent wants to render.</p>
+ <span>browsing context</span>, the user agent should <span>create a
+ <code>Document</code> object</span>, mark it as being an <span
+ title="HTML documents">HTML document</span>, and then either
+ associate that <code>Document</code> with a custom rendering that is
+ not rendered using the normal <code>Document</code> rendering rules,
+ or mutate that <code>Document</code> until it represents the content
+ the user agent wants to render.</p>
<!-- next two paragraphs are similar to the navigate-text section,
keep them in sync -->
@@ -64959,8 +64995,8 @@
<pre class="idl">interface <dfn>DragEvent</dfn> : MouseEvent {
readonly attribute <span>DataTransfer</span> <span title="dom-DragEvent-dataTransfer">dataTransfer</span>;
- void <span title="dom-DragEvent-initDragEvent">initDragEvent</span>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in <span>DataTransfer</span> dataTransferArg);
- void <span title="dom-DragEvent-initDragEventNS">initDragEventNS</span>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in AbstractView viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in DOMString modifiersListArg, in <span>DataTransfer</span> dataTransferArg);
+ void <span title="dom-DragEvent-initDragEvent">initDragEvent</span>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in <span>AbstractView</span> viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in boolean ctrlKeyArg, in boolean altKeyArg, in boolean shiftKeyArg, in boolean metaKeyArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in <span>DataTransfer</span> dataTransferArg);
+ void <span title="dom-DragEvent-initDragEventNS">initDragEventNS</span>(in DOMString namespaceURIArg, in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in <span>AbstractView</span> viewArg, in long detailArg, in long screenXArg, in long screenYArg, in long clientXArg, in long clientYArg, in unsigned short buttonArg, in EventTarget relatedTargetArg, in DOMString modifiersListArg, in <span>DataTransfer</span> dataTransferArg);
};</pre>
<dl class="domintro">
More information about the Commit-Watchers
mailing list