Browse files

[giow] (2) Drop DOM Views support.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9336

git-svn-id: http://svn.whatwg.org/webapps@4948 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
1 parent a08d239 commit f6f145d6eb44f40c7977d3d2f08dece686dccfee @Hixie Hixie committed Apr 2, 2010
Showing with 288 additions and 404 deletions.
  1. +96 −130 complete.html
  2. +96 −130 index
  3. +96 −144 source
View
226 complete.html
@@ -5530,10 +5530,10 @@ <h4 id=mq><span class=secno>2.4.10 </span>Media queries</h4>
<code title="">media_query_list</code> production of the Media
Queries specification. <a href=#refsMQ>[MQ]</a></p>
- <p>A string <dfn id=matches-the-environment>matches the environment</dfn> of a view if it is
+ <p>A string <dfn id=matches-the-environment>matches the environment</dfn> of the user if it is
the empty string, a string consisting of only <a href=#space-character title="space
character">space characters</a>, or is a media query that matches
- that view's environment according to the definitions given in the
+ the user's environment according to the definitions given in the
Media Queries specification. <a href=#refsMQ>[MQ]</a></p>
@@ -7573,6 +7573,7 @@ <h4 id=documents-in-the-dom><span class=secno>3.1.1 </span>Documents in the DOM<
void <a href=#dom-document-writeln title=dom-document-writeln>writeln</a>(in DOMString... text);
// <a href=#editing>user interaction</a>
+ readonly attribute <a href=#windowproxy>WindowProxy</a> <a href=#dom-document-defaultview title=dom-document-defaultView>defaultView</a>;
<a href=#selection-0>Selection</a> <a href=#dom-document-getselection title=dom-document-getSelection>getSelection</a>();
readonly attribute <a href=#element>Element</a> <a href=#dom-document-activeelement title=dom-document-activeElement>activeElement</a>;
boolean <a href=#dom-document-hasfocus title=dom-document-hasFocus>hasFocus</a>();
@@ -11857,9 +11858,9 @@ <h4 id=the-link-element><span class=secno>4.2.4 </span>The <dfn><code>link</code
<p>However, if the link is an <a href=#external-resource-link>external resource link</a>,
then the <code title=attr-link-media><a href=#attr-link-media>media</a></code> attribute is
- prescriptive. The user agent must apply the external resource to a
- <a href=#view>view</a> when the <code title=attr-link-media><a href=#attr-link-media>media</a></code> attribute's value <a href=#matches-the-environment>matches
- the environment</a> of that view and the other relevant
+ prescriptive. The user agent must apply the external resource when
+ the <code title=attr-link-media><a href=#attr-link-media>media</a></code> attribute's value
+ <a href=#matches-the-environment>matches the environment</a> and the other relevant
conditions apply, and must not apply it otherwise.</p><!-- note
similar text in <style> section -->
@@ -13007,10 +13008,10 @@ <h4 id=the-style-element><span class=secno>4.2.6 </span>The <dfn><code>style</co
<p>The <dfn id=attr-style-media title=attr-style-media><code>media</code></dfn>
attribute says which media the styles apply to. The value must be a
<a href=#valid-media-query>valid media query</a>. <span class=impl>The user agent
- must apply the styles to a <a href=#view>view</a> when the <code title=attr-style-media><a href=#attr-style-media>media</a></code> attribute's value
- <a href=#matches-the-environment>matches the environment</a> of that view and the other
- relevant conditions apply, and must not apply them
- otherwise.</span></p><!-- note similar text in <link> section -->
+ must apply the styles when the <code title=attr-style-media><a href=#attr-style-media>media</a></code> attribute's value
+ <a href=#matches-the-environment>matches the environment</a> and the other relevant
+ conditions apply, and must not apply them otherwise.</span></p><!--
+ note similar text in <link> section -->
<div class=impl>
@@ -19397,14 +19398,6 @@ <h4 id=the-img-element><span class=secno>4.8.1 </span>The <dfn><code>img</code><
attribute's value is the empty string, or if the conditions in the
previous paragraph are not met, then the image is <em>not</em> <i title=img-available><a href=#img-available>available</a></i>.</p>
- <p class=note>An image might be <i title=img-available><a href=#img-available>available</a></i> in one <a href=#view>view</a> but not
- another. For instance, a <code><a href=#document>Document</a></code> could be rendered by
- a screen reader providing a speech synthesis view of the output of a
- Web browser using the screen media. In this case, the image would be
- <i title=img-available><a href=#img-available>available</a></i> in the Web browser's screen
- view, but <em>not</em> <i title=img-available><a href=#img-available>available</a></i> in the
- screen reader's view.</p>
-
<p>Whether the image is fetched successfully or not (e.g. whether
the response code was a 2xx code <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>) must be
ignored when determining the image's type and whether it is a valid
@@ -23704,8 +23697,9 @@ <h5 id=loading-the-media-resource><span class=secno>4.8.9.5 </span>Loading the m
<li><p>&#8987; If <var title="">candidate</var> has a <code title=attr-source-media><a href=#attr-source-media>media</a></code> attribute whose value does
not <a href=#matches-the-environment title="matches the environment">match the
- environment</a> of the <a href=#default-view>default view</a>, then end the
- <a href=#synchronous-section>synchronous section</a>, and jump down to the <i title="">failed</i> step below.</li>
+ environment</a>, then end the <a href=#synchronous-section>synchronous
+ section</a>, and jump down to the <i title="">failed</i> step
+ below.</li>
<li><p>&#8987; Set the <code title=dom-media-currentSrc><a href=#dom-media-currentsrc>currentSrc</a></code> attribute to <var title="">absolute URL</var>.</li>
@@ -53073,69 +53067,21 @@ <h3 id=windows><span class=secno>6.1 </span>Browsing contexts</h3>
<a href=#browsing-context>browsing context</a> is designated the <dfn id=active-document>active
document</dfn>.</p>
- <p>Each <code><a href=#document>Document</a></code> has a collection of one or more <a href=#view title=view>views</a>.</p>
-
- <p>A <dfn id=view>view</dfn> is a user agent interface tied to a particular
- media used for the presentation of a particular
- <code><a href=#document>Document</a></code> object in some media. A view may be
- interactive. Each view is represented by an
- <code>AbstractView</code> object. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
-
- <p>The main <a href=#view>view</a> through which a user primarily
- interacts with a user agent is the <dfn id=default-view>default view</dfn>. The
- <code>AbstractView</code> object that represents this view <span class=impl>must also implement the <code><a href=#window>Window</a></code> interface,
- and</span> is referred to as the <code><a href=#document>Document</a></code>'s
- <code><a href=#window>Window</a></code> object. <code><a href=#windowproxy>WindowProxy</a></code> objects forward
- everything to the <a href=#active-document>active document</a>'s <a href=#default-view>default
- view</a>'s <code><a href=#window>Window</a></code> object.</p>
-
- <div class=impl>
-
- <p>The <code title=dom-document-defaultView>defaultView</code>
- attribute on the <code><a href=#document>Document</a></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=#refsDOMVIEWS>[DOMVIEWS]</a></p>
-
- </div>
-
- <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><a href=#document>Document</a></code> object. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
+ <p>Each <code><a href=#document>Document</a></code> is associated with a
+ <code><a href=#window>Window</a></code> object. A <a href=#browsing-context>browsing context</a>'s
+ <code><a href=#windowproxy>WindowProxy</a></code> object forwards everything to the
+ <a href=#browsing-context>browsing context</a>'s <a href=#active-document>active document</a>'s
+ <code><a href=#window>Window</a></code> object.</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><a href=#document>Document</a></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><a href=#document>Document</a></code> in the
- same <a href=#browsing-context>browsing context</a>, such that the mapping is then
+ one particular case, a <code><a href=#window>Window</a></code> can be reused for the
+ presentation of a second <code><a href=#document>Document</a></code> in the same
+ <a href=#browsing-context>browsing context</a>, such that the mapping is then
2-to-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><a href=#document>Document</a></code> to another, with
<a href=#replacement-enabled>replacement enabled</a>.</p>
- <div class=impl>
-
- <p>Events that use the <code><a href=#uievent>UIEvent</a></code> interface are related to
- a specific <a href=#view>view</a> (the view in which the event happened);
- when that <a href=#view>view</a> is the <a href=#default-view>default view</a>, the
- event object's <code title="">view</code> attribute's must return
- the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
- context</a> of that <a href=#view>view</a>, not the actual
- <code>AbstractView</code> object of the <a href=#default-view>default
- view</a>. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
-
- </div>
-
- <p class=note>A typical Web browser has one obvious
- <a href=#view>view</a> per <code><a href=#document>Document</a></code>: the browser's window
- (screen media). This is typically the <a href=#default-view>default view</a>. If
- a page is printed, however, a second view becomes evident, that of
- the print media. The two views always share the same underlying
- <code><a href=#document>Document</a></code> object, but they have a different presentation
- of that object. A speech browser might have a different
- <a href=#default-view>default view</a>, using the speech media.</p>
-
<p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a
<a href=#browsing-context>browsing context</a> associated with it. In particular,
data mining tools are likely to never instantiate browsing
@@ -53581,6 +53527,7 @@ <h3 id=the-window-object><span class=secno>6.2 </span>The <code><a href=#window>
// the current browsing context
readonly attribute <a href=#windowproxy>WindowProxy</a> <a href=#dom-window title=dom-window>window</a>;
readonly attribute <a href=#windowproxy>WindowProxy</a> <a href=#dom-self title=dom-self>self</a>;
+ readonly attribute <a href=#document>Document</a> <a href=#dom-document title=dom-document>document</a>;
attribute DOMString <a href=#dom-name title=dom-name>name</a>;
[PutForwards=<a href=#dom-location-href title=dom-location-href>href</a>] readonly attribute <a href=#location>Location</a> <a href=#dom-location title=dom-location>location</a>;
readonly attribute <a href=#history-0>History</a> <a href=#dom-history title=dom-history>history</a>;
@@ -53713,12 +53660,40 @@ <h3 id=the-window-object><span class=secno>6.2 </span>The <code><a href=#window>
</dd>
+
+ <dt><var title="">window</var> . <code title=dom-document><a href=#dom-document>document</a></code></dt>
+
+ <dd>
+
+ <p>Returns the <a href=#active-document>active document</a>.</p>
+
+ </dd>
+
+
+ <dt><var title="">document</var> . <code title=dom-document-defaultView><a href=#dom-document-defaultview>defaultView</a></code></dt>
+
+ <dd>
+
+ <p>Returns the <code><a href=#window>Window</a></code> object of the <a href=#active-document>active document</a>.</p>
+
+ </dd>
+
</dl><div class=impl>
<p>The <dfn id=dom-window title=dom-window><code>window</code></dfn>, <dfn id=dom-frames title=dom-frames><code>frames</code></dfn>, and <dfn id=dom-self title=dom-self><code>self</code></dfn> IDL attributes must all
return the <code><a href=#window>Window</a></code> object's <a href=#browsing-context>browsing
context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+ <p>The <dfn id=dom-document title=dom-document><code>document</code></dfn> IDL
+ attribute must return the <code><a href=#document>Document</a></code> object of the
+ <code><a href=#window>Window</a></code> object's <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing
+ context</a>'s <a href=#active-document>active document</a>.</p>
+
+ <p>The <dfn id=dom-document-defaultview title=dom-document-defaultView><code>defaultView</code></dfn> IDL
+ attribute of the <code><a href=#htmldocument>HTMLDocument</a></code> interface must return the
+ <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a>'s
+ <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+
</div>
@@ -54045,9 +54020,16 @@ <h4 id=garbage-collection-and-browsing-contexts><span class=secno>6.2.5 </span>G
and the user agent itself has a strong reference to its <a href=#top-level-browsing-context title="top-level browsing context">top-level browsing
contexts</a>.</p>
- <p>A <code><a href=#document>Document</a></code> has a strong reference to each of its
- <a href=#view title=view>views</a> and their <code>AbstractView</code>
- objects.</p>
+ <p>A <code><a href=#document>Document</a></code> has a strong reference to its
+ <code><a href=#window>Window</a></code> object.</p>
+
+ <p class=note>A <code><a href=#window>Window</a></code> object <a href=#implied-strong-reference title="implied
+ strong reference">has a strong reference</a> to its
+ <code><a href=#document>Document</a></code> object through its <code title=dom-document><a href=#dom-document>document</a></code> attribute. Thus, references
+ from other scripts to either of those objects will keep both
+ alive. Similarly, both <code><a href=#document>Document</a></code> and <code><a href=#window>Window</a></code>
+ objects have <a href=#implied-strong-reference title="implied strong reference">implied strong
+ references</a> to the <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
<p>Each <a href=#concept-script title=concept-script>script</a> has a strong
reference to its <a href="#script's-browsing-context" title="script's browsing context">browsing
@@ -54077,14 +54059,7 @@ <h4 id=garbage-collection-and-browsing-contexts><span class=secno>6.2.5 </span>G
<a href=#browsing-context>browsing context</a> to the
<code><a href=#document>Document</a></code>.</li>
- </ol><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</a> to its
- <code><a href=#document>Document</a></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><a href=#document>Document</a></code> object is <a href=#discard-a-document title="discard a Document">discarded</a>, it is also removed from
+ </ol><p class=note>Whenever a <code><a href=#document>Document</a></code> object is <a href=#discard-a-document title="discard a Document">discarded</a>, it is also removed from
the list of <a href="#the-worker's-documents">the worker's <code>Document</code>s</a> of each
worker whose list contains that <code><a href=#document>Document</a></code>.</p>
@@ -54191,20 +54166,20 @@ <h4 id=browser-interface-elements><span class=secno>6.2.6 </span>Browser interfa
<dt><dfn id=the-status-bar-barprop-object>The status bar <code>BarProp</code> object</dfn></dt>
<dd>Represents a user interface element found immediately below or
- after the document, as appropriate for the <a href=#default-view>default
- view</a>'s media. If the user agent has no such user interface
- element, then the object may act as if the corresponding user
- interface element was absent (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code> attribute may return
- false).</dd>
+ after the document, as appropriate for the user's media. If the
+ user agent has no such user interface element, then the object may
+ act as if the corresponding user interface element was absent
+ (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code>
+ attribute may return false).</dd>
<dt><dfn id=the-toolbar-barprop-object>The toolbar <code>BarProp</code> object</dfn></dt>
<dd>Represents the user interface element found immediately above
- or before the document, as appropriate for the <a href=#default-view>default
- view</a>'s media. If the user agent has no such user interface
- element, then the object may act as if the corresponding user
- interface element was absent (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code> attribute may return
- false).</dd>
+ or before the document, as appropriate for the user's media. If the
+ user agent has no such user interface element, then the object may
+ act as if the corresponding user interface element was absent
+ (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code>
+ attribute may return false).</dd>
</dl><p>The <dfn id=dom-window-locationbar title=dom-window-locationbar><code>locationbar</code></dfn>
attribute must return <a href=#the-location-bar-barprop-object>the location bar <code>BarProp</code>
@@ -55834,18 +55809,17 @@ <h4 id=navigating-across-documents><span class=secno>6.5.1 </span>Navigating acr
<p><dfn id=create-a-document-object title="create a Document object">Creating a new
<code>Document</code> object</dfn>: When a <code><a href=#document>Document</a></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
+ is created as part of the above steps, a new <code><a href=#window>Window</a></code>
+ object must be created and associated with the
<code><a href=#document>Document</a></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><a href=#document>Document</a></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><a href=#document>Document</a></code> has the <a href=#same-origin>same origin</a> as the new
- <code><a href=#document>Document</a></code>, then the <code><a href=#window>Window</a></code> object and
- associated <a href=#view title=view>views</a> of that
- <code><a href=#document>Document</a></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><a href=#document>Document</a></code>, then the <code><a href=#window>Window</a></code> object of that
+ <code><a href=#document>Document</a></code> must be used instead, and the <code title=dom-document><a href=#dom-document>document</a></code> attribute of the
+ <code><a href=#window>Window</a></code> object must be changed to point to the new
<code><a href=#document>Document</a></code> instead.</p>
</li>
@@ -56437,9 +56411,9 @@ <h4 id=history-traversal><span class=secno>6.5.9 </span>History traversal</h4> <
<a href=#scroll-to-the-fragment-identifier>scroll to the fragment identifier</a>.</li>
<li><p>If the entry is <a href=#an-entry-with-persisted-user-state>an entry with persisted user
- state</a>, the user agent may update aspects of the document
- view, for instance the scroll position or values of form fields,
- that it had previously recorded.</li>
+ state</a>, the user agent may update aspects of the document and
+ its rendering, for instance the scroll position or values of form
+ fields, that it had previously recorded.</li>
<li>
@@ -63198,7 +63172,7 @@ <h4 id=the-dragevent-and-datatransfer-interfaces><span class=secno>8.9.2 </span>
<pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : <span>MouseEvent</span> {
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 <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-initdragevent title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in any dummyArg<!-- used to be viewArg, back when we had views -->, 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);
};</pre>
<dl class=domintro><dt><var title="">event</var> . <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code></dt>
@@ -63213,7 +63187,8 @@ <h4 id=the-dragevent-and-datatransfer-interfaces><span class=secno>8.9.2 </span>
<p>The <dfn id=dom-dragevent-initdragevent title=dom-DragEvent-initDragEvent><code>initDragEvent()</code></dfn>
method must initialize the event in a manner analogous to the
- similarly-named method in the DOM Events interfaces. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
+ similarly-named method in the DOM Events interfaces, except that the
+ <var title="">dummyArg</var> argument must be ignored. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<p>The <dfn id=dom-dragevent-datatransfer title=dom-DragEvent-dataTransfer><code>dataTransfer</code></dfn>
attribute of the <code><a href=#dragevent>DragEvent</a></code> interface represents the
@@ -63448,16 +63423,16 @@ <h4 id=dndevents><span class=secno>8.9.3 </span>Events fired during a drag-and-d
<div class=impl>
- <p>Whenever the processing model described
- below causes one of these events to be fired, the event fired must
- use the <code><a href=#dragevent>DragEvent</a></code> interface defined above, must have
- the bubbling and cancelable behaviors given in the table below, and
- must have the context information set up as described after the
- table, with the <code title=dom-UIEvent-view>view</code> attribute
- set to the view with which the user interacted to trigger the
- drag-and-drop event, the <code title=dom-UIEvent-detail>detail</code> attribute set to zero, the
- mouse and key attributes set according to the state of the input
- devices as they would be for user interaction events, and the <code title="">relatedTarget</code> attribute set to null.</p>
+ <p>Whenever the processing model described below causes one of these
+ events to be fired, the event fired must use the
+ <code><a href=#dragevent>DragEvent</a></code> interface defined above, must have the
+ bubbling and cancelable behaviors given in the table below, and must
+ have the context information set up as described after the table,
+ with the <code title=dom-UIEvent-detail>detail</code> attribute
+ set to zero, the mouse and key attributes set according to the state
+ of the input devices as they would be for user interaction events,
+ and the <code title="">relatedTarget</code> attribute set to
+ null.</p>
<p>If there is no relevant pointing device, the object must have its
<code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes set to 0.</p>
@@ -64100,10 +64075,6 @@ <h5 id=when-the-drag-and-drop-operation-starts-or-ends-in-another-document><span
model must be followed as described above, irrespective of how many
documents are involved in the operation.</p>
- <!-- should we mention that you shouldn't include the view from the
- source in the events to the target, or is that obvious enough from
- the requirements in the event section above? -->
-
</div>
@@ -83691,8 +83662,8 @@ <h3 id=frames-and-framesets><span class=secno>14.5 </span>Frames and framesets</
<p>When an <code><a href=#the-html-element-0>html</a></code> element's second child element is a
<code><a href=#frameset>frameset</a></code> element, the user agent is expected to render
the <code><a href=#frameset>frameset</a></code> element as described below across the
- surface of the <a href=#view>view</a>, instead of applying the usual CSS
- rendering rules.</p>
+ surface of the viewport, instead of applying the usual CSS rendering
+ rules.</p>
<p>When rendering a <code><a href=#frameset>frameset</a></code> on a surface, the user
agent is expected to use the following layout algorithm:</p>
@@ -84051,8 +84022,8 @@ <h3 id=print-media><span class=secno>14.7 </span>Print media</h3>
<p>When the user actually <a href=#obtain-a-physical-form title="obtain a physical
form">obtains a physical form</a> (or a representation of a
physical form) of a <code><a href=#document>Document</a></code>, the user agent is
- expected to create a new view with the print media, render the
- result, and the discard the view.</p>
+ expected to create a new rendering of the <code><a href=#document>Document</a></code> for
+ the print media.</p>
@@ -89032,11 +89003,6 @@ <h3 class="no-num">Reflecting IDL attributes</h3>
Specification</a></cite>, J. Kesselman, J. Robie, M. Champion,
P. Sharpe, V. Apparao, L. Wood. W3C.</dd>
- <dt id=refsDOMVIEWS>[DOMVIEWS]</dt>
- <dd><cite><a href=http://www.w3.org/TR/DOM-Level-2-Views/>Document Object
- Model (DOM) Level 2 Views Specification</a></cite>, A. Le Hors, L.
- Cable. W3C.</dd>
-
<dt id=refsE163>[E163]</dt>
<dd><cite>Recommendation E.163 &mdash; Numbering Plan for The International
Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November
View
226 index
@@ -5428,10 +5428,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<code title="">media_query_list</code> production of the Media
Queries specification. <a href=#refsMQ>[MQ]</a></p>
- <p>A string <dfn id=matches-the-environment>matches the environment</dfn> of a view if it is
+ <p>A string <dfn id=matches-the-environment>matches the environment</dfn> of the user if it is
the empty string, a string consisting of only <a href=#space-character title="space
character">space characters</a>, or is a media query that matches
- that view's environment according to the definitions given in the
+ the user's environment according to the definitions given in the
Media Queries specification. <a href=#refsMQ>[MQ]</a></p>
@@ -7471,6 +7471,7 @@ interface <dfn id=htmldocument>HTMLDocument</dfn> {
void <a href=#dom-document-writeln title=dom-document-writeln>writeln</a>(in DOMString... text);
// <a href=#editing>user interaction</a>
+ readonly attribute <a href=#windowproxy>WindowProxy</a> <a href=#dom-document-defaultview title=dom-document-defaultView>defaultView</a>;
<a href=#selection-0>Selection</a> <a href=#dom-document-getselection title=dom-document-getSelection>getSelection</a>();
readonly attribute <a href=#element>Element</a> <a href=#dom-document-activeelement title=dom-document-activeElement>activeElement</a>;
boolean <a href=#dom-document-hasfocus title=dom-document-hasFocus>hasFocus</a>();
@@ -11755,9 +11756,9 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p&gt;
<p>However, if the link is an <a href=#external-resource-link>external resource link</a>,
then the <code title=attr-link-media><a href=#attr-link-media>media</a></code> attribute is
- prescriptive. The user agent must apply the external resource to a
- <a href=#view>view</a> when the <code title=attr-link-media><a href=#attr-link-media>media</a></code> attribute's value <a href=#matches-the-environment>matches
- the environment</a> of that view and the other relevant
+ prescriptive. The user agent must apply the external resource when
+ the <code title=attr-link-media><a href=#attr-link-media>media</a></code> attribute's value
+ <a href=#matches-the-environment>matches the environment</a> and the other relevant
conditions apply, and must not apply it otherwise.</p><!-- note
similar text in <style> section -->
@@ -12905,10 +12906,10 @@ people expect to have work and what is necessary.
<p>The <dfn id=attr-style-media title=attr-style-media><code>media</code></dfn>
attribute says which media the styles apply to. The value must be a
<a href=#valid-media-query>valid media query</a>. <span class=impl>The user agent
- must apply the styles to a <a href=#view>view</a> when the <code title=attr-style-media><a href=#attr-style-media>media</a></code> attribute's value
- <a href=#matches-the-environment>matches the environment</a> of that view and the other
- relevant conditions apply, and must not apply them
- otherwise.</span></p><!-- note similar text in <link> section -->
+ must apply the styles when the <code title=attr-style-media><a href=#attr-style-media>media</a></code> attribute's value
+ <a href=#matches-the-environment>matches the environment</a> and the other relevant
+ conditions apply, and must not apply them otherwise.</span></p><!--
+ note similar text in <link> section -->
<div class=impl>
@@ -19295,14 +19296,6 @@ interface <dfn id=htmlimageelement>HTMLImageElement</dfn> : <a href=#htmlelement
attribute's value is the empty string, or if the conditions in the
previous paragraph are not met, then the image is <em>not</em> <i title=img-available><a href=#img-available>available</a></i>.</p>
- <p class=note>An image might be <i title=img-available><a href=#img-available>available</a></i> in one <a href=#view>view</a> but not
- another. For instance, a <code><a href=#document>Document</a></code> could be rendered by
- a screen reader providing a speech synthesis view of the output of a
- Web browser using the screen media. In this case, the image would be
- <i title=img-available><a href=#img-available>available</a></i> in the Web browser's screen
- view, but <em>not</em> <i title=img-available><a href=#img-available>available</a></i> in the
- screen reader's view.</p>
-
<p>Whether the image is fetched successfully or not (e.g. whether
the response code was a 2xx code <a href=#concept-http-equivalent-codes title=concept-http-equivalent-codes>or equivalent</a>) must be
ignored when determining the image's type and whether it is a valid
@@ -23605,8 +23598,9 @@ interface <dfn>CueRangeCallback</dfn> {
<li><p>&#8987; If <var title="">candidate</var> has a <code title=attr-source-media><a href=#attr-source-media>media</a></code> attribute whose value does
not <a href=#matches-the-environment title="matches the environment">match the
- environment</a> of the <a href=#default-view>default view</a>, then end the
- <a href=#synchronous-section>synchronous section</a>, and jump down to the <i title="">failed</i> step below.</li>
+ environment</a>, then end the <a href=#synchronous-section>synchronous
+ section</a>, and jump down to the <i title="">failed</i> step
+ below.</li>
<li><p>&#8987; Set the <code title=dom-media-currentSrc><a href=#dom-media-currentsrc>currentSrc</a></code> attribute to <var title="">absolute URL</var>.</li>
@@ -52974,69 +52968,21 @@ _:n2 hcard:adr%20street-address "Avenue Q" ;
<a href=#browsing-context>browsing context</a> is designated the <dfn id=active-document>active
document</dfn>.</p>
- <p>Each <code><a href=#document>Document</a></code> has a collection of one or more <a href=#view title=view>views</a>.</p>
-
- <p>A <dfn id=view>view</dfn> is a user agent interface tied to a particular
- media used for the presentation of a particular
- <code><a href=#document>Document</a></code> object in some media. A view may be
- interactive. Each view is represented by an
- <code>AbstractView</code> object. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
-
- <p>The main <a href=#view>view</a> through which a user primarily
- interacts with a user agent is the <dfn id=default-view>default view</dfn>. The
- <code>AbstractView</code> object that represents this view <span class=impl>must also implement the <code><a href=#window>Window</a></code> interface,
- and</span> is referred to as the <code><a href=#document>Document</a></code>'s
- <code><a href=#window>Window</a></code> object. <code><a href=#windowproxy>WindowProxy</a></code> objects forward
- everything to the <a href=#active-document>active document</a>'s <a href=#default-view>default
- view</a>'s <code><a href=#window>Window</a></code> object.</p>
-
- <div class=impl>
-
- <p>The <code title=dom-document-defaultView>defaultView</code>
- attribute on the <code><a href=#document>Document</a></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=#refsDOMVIEWS>[DOMVIEWS]</a></p>
-
- </div>
-
- <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><a href=#document>Document</a></code> object. <a href=#refsDOMVIEWS>[DOMVIEWS]</a></p>
+ <p>Each <code><a href=#document>Document</a></code> is associated with a
+ <code><a href=#window>Window</a></code> object. A <a href=#browsing-context>browsing context</a>'s
+ <code><a href=#windowproxy>WindowProxy</a></code> object forwards everything to the
+ <a href=#browsing-context>browsing context</a>'s <a href=#active-document>active document</a>'s
+ <code><a href=#window>Window</a></code> object.</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><a href=#document>Document</a></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><a href=#document>Document</a></code> in the
- same <a href=#browsing-context>browsing context</a>, such that the mapping is then
+ one particular case, a <code><a href=#window>Window</a></code> can be reused for the
+ presentation of a second <code><a href=#document>Document</a></code> in the same
+ <a href=#browsing-context>browsing context</a>, such that the mapping is then
2-to-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><a href=#document>Document</a></code> to another, with
<a href=#replacement-enabled>replacement enabled</a>.</p>
- <div class=impl>
-
- <p>Events that use the <code><a href=#uievent>UIEvent</a></code> interface are related to
- a specific <a href=#view>view</a> (the view in which the event happened);
- when that <a href=#view>view</a> is the <a href=#default-view>default view</a>, the
- event object's <code title="">view</code> attribute's must return
- the <code><a href=#windowproxy>WindowProxy</a></code> object of the <a href=#browsing-context>browsing
- context</a> of that <a href=#view>view</a>, not the actual
- <code>AbstractView</code> object of the <a href=#default-view>default
- view</a>. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
-
- </div>
-
- <p class=note>A typical Web browser has one obvious
- <a href=#view>view</a> per <code><a href=#document>Document</a></code>: the browser's window
- (screen media). This is typically the <a href=#default-view>default view</a>. If
- a page is printed, however, a second view becomes evident, that of
- the print media. The two views always share the same underlying
- <code><a href=#document>Document</a></code> object, but they have a different presentation
- of that object. A speech browser might have a different
- <a href=#default-view>default view</a>, using the speech media.</p>
-
<p class=note>A <code><a href=#document>Document</a></code> does not necessarily have a
<a href=#browsing-context>browsing context</a> associated with it. In particular,
data mining tools are likely to never instantiate browsing
@@ -53482,6 +53428,7 @@ interface <dfn id=window>Window</dfn> {
// the current browsing context
readonly attribute <a href=#windowproxy>WindowProxy</a> <a href=#dom-window title=dom-window>window</a>;
readonly attribute <a href=#windowproxy>WindowProxy</a> <a href=#dom-self title=dom-self>self</a>;
+ readonly attribute <a href=#document>Document</a> <a href=#dom-document title=dom-document>document</a>;
attribute DOMString <a href=#dom-name title=dom-name>name</a>;
[PutForwards=<a href=#dom-location-href title=dom-location-href>href</a>] readonly attribute <a href=#location>Location</a> <a href=#dom-location title=dom-location>location</a>;
readonly attribute <a href=#history-0>History</a> <a href=#dom-history title=dom-history>history</a>;
@@ -53614,12 +53561,40 @@ interface <dfn id=window>Window</dfn> {
</dd>
+
+ <dt><var title="">window</var> . <code title=dom-document><a href=#dom-document>document</a></code></dt>
+
+ <dd>
+
+ <p>Returns the <a href=#active-document>active document</a>.</p>
+
+ </dd>
+
+
+ <dt><var title="">document</var> . <code title=dom-document-defaultView><a href=#dom-document-defaultview>defaultView</a></code></dt>
+
+ <dd>
+
+ <p>Returns the <code><a href=#window>Window</a></code> object of the <a href=#active-document>active document</a>.</p>
+
+ </dd>
+
</dl><div class=impl>
<p>The <dfn id=dom-window title=dom-window><code>window</code></dfn>, <dfn id=dom-frames title=dom-frames><code>frames</code></dfn>, and <dfn id=dom-self title=dom-self><code>self</code></dfn> IDL attributes must all
return the <code><a href=#window>Window</a></code> object's <a href=#browsing-context>browsing
context</a>'s <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+ <p>The <dfn id=dom-document title=dom-document><code>document</code></dfn> IDL
+ attribute must return the <code><a href=#document>Document</a></code> object of the
+ <code><a href=#window>Window</a></code> object's <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing
+ context</a>'s <a href=#active-document>active document</a>.</p>
+
+ <p>The <dfn id=dom-document-defaultview title=dom-document-defaultView><code>defaultView</code></dfn> IDL
+ attribute of the <code><a href=#htmldocument>HTMLDocument</a></code> interface must return the
+ <code><a href=#document>Document</a></code>'s <a href=#browsing-context>browsing context</a>'s
+ <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
+
</div>
@@ -53946,9 +53921,16 @@ interface <dfn id=window>Window</dfn> {
and the user agent itself has a strong reference to its <a href=#top-level-browsing-context title="top-level browsing context">top-level browsing
contexts</a>.</p>
- <p>A <code><a href=#document>Document</a></code> has a strong reference to each of its
- <a href=#view title=view>views</a> and their <code>AbstractView</code>
- objects.</p>
+ <p>A <code><a href=#document>Document</a></code> has a strong reference to its
+ <code><a href=#window>Window</a></code> object.</p>
+
+ <p class=note>A <code><a href=#window>Window</a></code> object <a href=#implied-strong-reference title="implied
+ strong reference">has a strong reference</a> to its
+ <code><a href=#document>Document</a></code> object through its <code title=dom-document><a href=#dom-document>document</a></code> attribute. Thus, references
+ from other scripts to either of those objects will keep both
+ alive. Similarly, both <code><a href=#document>Document</a></code> and <code><a href=#window>Window</a></code>
+ objects have <a href=#implied-strong-reference title="implied strong reference">implied strong
+ references</a> to the <code><a href=#windowproxy>WindowProxy</a></code> object.</p>
<p>Each <a href=#concept-script title=concept-script>script</a> has a strong
reference to its <a href="#script's-browsing-context" title="script's browsing context">browsing
@@ -53978,14 +53960,7 @@ interface <dfn id=window>Window</dfn> {
<a href=#browsing-context>browsing context</a> to the
<code><a href=#document>Document</a></code>.</li>
- </ol><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</a> to its
- <code><a href=#document>Document</a></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><a href=#document>Document</a></code> object is <a href=#discard-a-document title="discard a Document">discarded</a>, it is also removed from
+ </ol><p class=note>Whenever a <code><a href=#document>Document</a></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><a href=#document>Document</a></code>s</span> of each
worker whose list contains that <code><a href=#document>Document</a></code>.</p>
@@ -54092,20 +54067,20 @@ interface <dfn id=window>Window</dfn> {
<dt><dfn id=the-status-bar-barprop-object>The status bar <code>BarProp</code> object</dfn></dt>
<dd>Represents a user interface element found immediately below or
- after the document, as appropriate for the <a href=#default-view>default
- view</a>'s media. If the user agent has no such user interface
- element, then the object may act as if the corresponding user
- interface element was absent (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code> attribute may return
- false).</dd>
+ after the document, as appropriate for the user's media. If the
+ user agent has no such user interface element, then the object may
+ act as if the corresponding user interface element was absent
+ (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code>
+ attribute may return false).</dd>
<dt><dfn id=the-toolbar-barprop-object>The toolbar <code>BarProp</code> object</dfn></dt>
<dd>Represents the user interface element found immediately above
- or before the document, as appropriate for the <a href=#default-view>default
- view</a>'s media. If the user agent has no such user interface
- element, then the object may act as if the corresponding user
- interface element was absent (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code> attribute may return
- false).</dd>
+ or before the document, as appropriate for the user's media. If the
+ user agent has no such user interface element, then the object may
+ act as if the corresponding user interface element was absent
+ (i.e. its <code title=dom-BarProp-visible><a href=#dom-barprop-visible>visible</a></code>
+ attribute may return false).</dd>
</dl><p>The <dfn id=dom-window-locationbar title=dom-window-locationbar><code>locationbar</code></dfn>
attribute must return <a href=#the-location-bar-barprop-object>the location bar <code>BarProp</code>
@@ -55735,18 +55710,17 @@ State: &lt;OUTPUT NAME=I&gt;1&lt;/OUTPUT&gt; &lt;INPUT VALUE="Increment" TYPE=BU
<p><dfn id=create-a-document-object title="create a Document object">Creating a new
<code>Document</code> object</dfn>: When a <code><a href=#document>Document</a></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
+ is created as part of the above steps, a new <code><a href=#window>Window</a></code>
+ object must be created and associated with the
<code><a href=#document>Document</a></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><a href=#document>Document</a></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><a href=#document>Document</a></code> has the <a href=#same-origin>same origin</a> as the new
- <code><a href=#document>Document</a></code>, then the <code><a href=#window>Window</a></code> object and
- associated <a href=#view title=view>views</a> of that
- <code><a href=#document>Document</a></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><a href=#document>Document</a></code>, then the <code><a href=#window>Window</a></code> object of that
+ <code><a href=#document>Document</a></code> must be used instead, and the <code title=dom-document><a href=#dom-document>document</a></code> attribute of the
+ <code><a href=#window>Window</a></code> object must be changed to point to the new
<code><a href=#document>Document</a></code> instead.</p>
</li>
@@ -56338,9 +56312,9 @@ State: &lt;OUTPUT NAME=I&gt;1&lt;/OUTPUT&gt; &lt;INPUT VALUE="Increment" TYPE=BU
<a href=#scroll-to-the-fragment-identifier>scroll to the fragment identifier</a>.</li>
<li><p>If the entry is <a href=#an-entry-with-persisted-user-state>an entry with persisted user
- state</a>, the user agent may update aspects of the document
- view, for instance the scroll position or values of form fields,
- that it had previously recorded.</li>
+ state</a>, the user agent may update aspects of the document and
+ its rendering, for instance the scroll position or values of form
+ fields, that it had previously recorded.</li>
<li>
@@ -63125,7 +63099,7 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
<pre class=idl>interface <dfn id=dragevent>DragEvent</dfn> : <span>MouseEvent</span> {
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 <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-initdragevent title=dom-DragEvent-initDragEvent>initDragEvent</a>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in any dummyArg<!-- used to be viewArg, back when we had views -->, 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);
};</pre>
<dl class=domintro><dt><var title="">event</var> . <code title=dom-DragEvent-dataTransfer><a href=#dom-dragevent-datatransfer>dataTransfer</a></code></dt>
@@ -63140,7 +63114,8 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
<p>The <dfn id=dom-dragevent-initdragevent title=dom-DragEvent-initDragEvent><code>initDragEvent()</code></dfn>
method must initialize the event in a manner analogous to the
- similarly-named method in the DOM Events interfaces. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
+ similarly-named method in the DOM Events interfaces, except that the
+ <var title="">dummyArg</var> argument must be ignored. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
<p>The <dfn id=dom-dragevent-datatransfer title=dom-DragEvent-dataTransfer><code>dataTransfer</code></dfn>
attribute of the <code><a href=#dragevent>DragEvent</a></code> interface represents the
@@ -63375,16 +63350,16 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
<div class=impl>
- <p>Whenever the processing model described
- below causes one of these events to be fired, the event fired must
- use the <code><a href=#dragevent>DragEvent</a></code> interface defined above, must have
- the bubbling and cancelable behaviors given in the table below, and
- must have the context information set up as described after the
- table, with the <code title=dom-UIEvent-view>view</code> attribute
- set to the view with which the user interacted to trigger the
- drag-and-drop event, the <code title=dom-UIEvent-detail>detail</code> attribute set to zero, the
- mouse and key attributes set according to the state of the input
- devices as they would be for user interaction events, and the <code title="">relatedTarget</code> attribute set to null.</p>
+ <p>Whenever the processing model described below causes one of these
+ events to be fired, the event fired must use the
+ <code><a href=#dragevent>DragEvent</a></code> interface defined above, must have the
+ bubbling and cancelable behaviors given in the table below, and must
+ have the context information set up as described after the table,
+ with the <code title=dom-UIEvent-detail>detail</code> attribute
+ set to zero, the mouse and key attributes set according to the state
+ of the input devices as they would be for user interaction events,
+ and the <code title="">relatedTarget</code> attribute set to
+ null.</p>
<p>If there is no relevant pointing device, the object must have its
<code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes set to 0.</p>
@@ -64027,10 +64002,6 @@ interface <dfn id=navigatorabilities>NavigatorAbilities</dfn> {
model must be followed as described above, irrespective of how many
documents are involved in the operation.</p>
- <!-- should we mention that you shouldn't include the view from the
- source in the events to the target, or is that obvious enough from
- the requirements in the event section above? -->
-
</div>
@@ -76963,8 +76934,8 @@ time:empty { binding: <i title="">time</i>; }</pre>
<p>When an <code><a href=#the-html-element-0>html</a></code> element's second child element is a
<code><a href=#frameset>frameset</a></code> element, the user agent is expected to render
the <code><a href=#frameset>frameset</a></code> element as described below across the
- surface of the <a href=#view>view</a>, instead of applying the usual CSS
- rendering rules.</p>
+ surface of the viewport, instead of applying the usual CSS rendering
+ rules.</p>
<p>When rendering a <code><a href=#frameset>frameset</a></code> on a surface, the user
agent is expected to use the following layout algorithm:</p>
@@ -77323,8 +77294,8 @@ time:empty { binding: <i title="">time</i>; }</pre>
<p>When the user actually <a href=#obtain-a-physical-form title="obtain a physical
form">obtains a physical form</a> (or a representation of a
physical form) of a <code><a href=#document>Document</a></code>, the user agent is
- expected to create a new view with the print media, render the
- result, and the discard the view.</p>
+ expected to create a new rendering of the <code><a href=#document>Document</a></code> for
+ the print media.</p>
@@ -82445,11 +82416,6 @@ interface <a href=#htmldocument>HTMLDocument</a> {
Specification</a></cite>, J. Kesselman, J. Robie, M. Champion,
P. Sharpe, V. Apparao, L. Wood. W3C.</dd>
- <dt id=refsDOMVIEWS>[DOMVIEWS]</dt>
- <dd><cite><a href=http://www.w3.org/TR/DOM-Level-2-Views/>Document Object
- Model (DOM) Level 2 Views Specification</a></cite>, A. Le Hors, L.
- Cable. W3C.</dd>
-
<dt id=refsE163>[E163]</dt>
<dd><cite>Recommendation E.163 &mdash; Numbering Plan for The International
Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November
View
240 source
@@ -4993,10 +4993,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
<code title="">media_query_list</code> production of the Media
Queries specification. <a href="#refsMQ">[MQ]</a></p>
- <p>A string <dfn>matches the environment</dfn> of a view if it is
+ <p>A string <dfn>matches the environment</dfn> of the user if it is
the empty string, a string consisting of only <span title="space
character">space characters</span>, or is a media query that matches
- that view's environment according to the definitions given in the
+ the user's environment according to the definitions given in the
Media Queries specification. <a href="#refsMQ">[MQ]</a></p>
@@ -7354,6 +7354,7 @@ interface <dfn>HTMLDocument</dfn> {
void <span title="dom-document-writeln">writeln</span>(in DOMString... text);
// <span>user interaction</span>
+ readonly attribute <span>WindowProxy</span> <span title="dom-document-defaultView">defaultView</span>;
<span>Selection</span> <span title="dom-document-getSelection">getSelection</span>();
readonly attribute <span>Element</span> <span title="dom-document-activeElement">activeElement</span>;
boolean <span title="dom-document-hasFocus">hasFocus</span>();
@@ -12269,10 +12270,9 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
<p>However, if the link is an <span>external resource link</span>,
then the <code title="attr-link-media">media</code> attribute is
- prescriptive. The user agent must apply the external resource to a
- <span>view</span> when the <code
- title="attr-link-media">media</code> attribute's value <span>matches
- the environment</span> of that view and the other relevant
+ prescriptive. The user agent must apply the external resource when
+ the <code title="attr-link-media">media</code> attribute's value
+ <span>matches the environment</span> and the other relevant
conditions apply, and must not apply it otherwise.</p><!-- note
similar text in <style> section -->
@@ -13600,11 +13600,11 @@ people expect to have work and what is necessary.
<p>The <dfn title="attr-style-media"><code>media</code></dfn>
attribute says which media the styles apply to. The value must be a
<span>valid media query</span>. <span class="impl">The user agent
- must apply the styles to a <span>view</span> when the <code
+ must apply the styles when the <code
title="attr-style-media">media</code> attribute's value
- <span>matches the environment</span> of that view and the other
- relevant conditions apply, and must not apply them
- otherwise.</span></p><!-- note similar text in <link> section -->
+ <span>matches the environment</span> and the other relevant
+ conditions apply, and must not apply them otherwise.</span></p><!--
+ note similar text in <link> section -->
<div class="impl">
@@ -20582,15 +20582,6 @@ interface <dfn>HTMLImageElement</dfn> : <span>HTMLElement</span> {
previous paragraph are not met, then the image is <em>not</em> <i
title="img-available">available</i>.</p>
- <p class="note">An image might be <i
- title="img-available">available</i> in one <span>view</span> but not
- another. For instance, a <code>Document</code> could be rendered by
- a screen reader providing a speech synthesis view of the output of a
- Web browser using the screen media. In this case, the image would be
- <i title="img-available">available</i> in the Web browser's screen
- view, but <em>not</em> <i title="img-available">available</i> in the
- screen reader's view.</p>
-
<p>Whether the image is fetched successfully or not (e.g. whether
the response code was a 2xx code <span
title="concept-http-equivalent-codes">or equivalent</span>) must be
@@ -25410,9 +25401,9 @@ interface <dfn>CueRangeCallback</dfn> {
<li><p>&#x231B; If <var title="">candidate</var> has a <code
title="attr-source-media">media</code> attribute whose value does
not <span title="matches the environment">match the
- environment</span> of the <span>default view</span>, then end the
- <span>synchronous section</span>, and jump down to the <i
- title="">failed</i> step below.</p></li>
+ environment</span>, then end the <span>synchronous
+ section</span>, and jump down to the <i title="">failed</i> step
+ below.</p></li>
<li><p>&#x231B; Set the <code
title="dom-media-currentSrc">currentSrc</code> attribute to <var
@@ -59701,74 +59692,22 @@ _:n2 hcard:adr%20street-address "Avenue Q" ;
<span>browsing context</span> is designated the <dfn>active
document</dfn>.</p>
- <p>Each <code>Document</code> has a collection of one or more <span
- title="view">views</span>.</p>
-
- <p>A <dfn>view</dfn> is a user agent interface tied to a particular
- media used for the presentation of a particular
- <code>Document</code> object in some media. A view may be
- interactive. Each view is represented by an
- <code>AbstractView</code> object. <a
- href="#refsDOMVIEWS">[DOMVIEWS]</a></p>
-
- <p>The main <span>view</span> through which a user primarily
- interacts with a user agent is the <dfn>default view</dfn>. The
- <code>AbstractView</code> object that represents this view <span
- class="impl">must also implement the <code>Window</code> interface,
- and</span> is referred to as the <code>Document</code>'s
- <code>Window</code> object. <code>WindowProxy</code> objects forward
- everything to the <span>active document</span>'s <span>default
- view</span>'s <code>Window</code> object.</p>
-
- <div class="impl">
-
- <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="#refsDOMVIEWS">[DOMVIEWS]</a></p>
-
- </div>
-
- <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="#refsDOMVIEWS">[DOMVIEWS]</a></p>
+ <p>Each <code>Document</code> is associated with a
+ <code>Window</code> object. A <span>browsing context</span>'s
+ <code>WindowProxy</code> object forwards everything to the
+ <span>browsing context</span>'s <span>active document</span>'s
+ <code>Window</code> object.</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
+ one particular case, a <code>Window</code> 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-to-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
- a specific <span>view</span> (the view in which the event happened);
- when that <span>view</span> is the <span>default view</span>, the
- event object's <code title="">view</code> attribute's must return
- the <code>WindowProxy</code> object of the <span>browsing
- context</span> of that <span>view</span>, not the actual
- <code>AbstractView</code> object of the <span>default
- view</span>. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
-
- </div>
-
- <p class="note">A typical Web browser has one obvious
- <span>view</span> per <code>Document</code>: the browser's window
- (screen media). This is typically the <span>default view</span>. If
- a page is printed, however, a second view becomes evident, that of
- the print media. The two views always share the same underlying
- <code>Document</code> object, but they have a different presentation
- of that object. A speech browser might have a different
- <span>default view</span>, using the speech media.</p>
-
<p class="note">A <code>Document</code> does not necessarily have a
<span>browsing context</span> associated with it. In particular,
data mining tools are likely to never instantiate browsing
@@ -60279,6 +60218,7 @@ interface <dfn>Window</dfn> {
// the current browsing context
readonly attribute <span>WindowProxy</span> <span title="dom-window">window</span>;
readonly attribute <span>WindowProxy</span> <span title="dom-self">self</span>;
+ readonly attribute <span>Document</span> <span title="dom-document">document</span>;
attribute DOMString <span title="dom-name">name</span>;
[PutForwards=<span title="dom-location-href">href</span>] readonly attribute <span>Location</span> <span title="dom-location">location</span>;
readonly attribute <span>History</span> <span title="dom-history">history</span>;
@@ -60413,6 +60353,24 @@ interface <dfn>Window</dfn> {
</dd>
+
+ <dt><var title="">window</var> . <code title="dom-document">document</code></dt>
+
+ <dd>
+
+ <p>Returns the <span>active document</span>.</p>
+
+ </dd>
+
+
+ <dt><var title="">document</var> . <code title="dom-document-defaultView">defaultView</code></dt>
+
+ <dd>
+
+ <p>Returns the <code>Window</code> object of the <span>active document</span>.</p>
+
+ </dd>
+
</dl>
<div class="impl">
@@ -60423,6 +60381,17 @@ interface <dfn>Window</dfn> {
return the <code>Window</code> object's <span>browsing
context</span>'s <code>WindowProxy</code> object.</p>
+ <p>The <dfn title="dom-document"><code>document</code></dfn> IDL
+ attribute must return the <code>Document</code> object of the
+ <code>Window</code> object's <code>Document</code>'s <span>browsing
+ context</span>'s <span>active document</span>.</p>
+
+ <p>The <dfn
+ title="dom-document-defaultView"><code>defaultView</code></dfn> IDL
+ attribute of the <code>HTMLDocument</code> interface must return the
+ <code>Document</code>'s <span>browsing context</span>'s
+ <code>WindowProxy</code> object.</p>
+
</div>
@@ -60803,9 +60772,17 @@ interface <dfn>Window</dfn> {
title="top-level browsing context">top-level browsing
contexts</span>.</p>
- <p>A <code>Document</code> has a strong reference to each of its
- <span title="view">views</span> and their <code>AbstractView</code>
- objects.</p>
+ <p>A <code>Document</code> has a strong reference to its
+ <code>Window</code> object.</p>
+
+ <p class="note">A <code>Window</code> object <span title="implied
+ strong reference">has a strong reference</span> to its
+ <code>Document</code> object through its <code
+ title="dom-document">document</code> attribute. Thus, references
+ from other scripts to either of those objects will keep both
+ alive. Similarly, both <code>Document</code> and <code>Window</code>
+ objects have <span title="implied strong reference">implied strong
+ references</span> to the <code>WindowProxy</code> object.</p>
<p>Each <span title="concept-script">script</span> has a strong
reference to its <span title="script's browsing context">browsing
@@ -60840,15 +60817,6 @@ interface <dfn>Window</dfn> {
</ol>
- <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</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
the list of <span>the worker's <code>Document</code>s</span> of each
@@ -60966,22 +60934,20 @@ interface <dfn>Window</dfn> {
<dt><dfn>The status bar <code>BarProp</code> object</dfn></dt>
<dd>Represents a user interface element found immediately below or
- after the document, as appropriate for the <span>default
- view</span>'s media. If the user agent has no such user interface
- element, then the object may act as if the corresponding user
- interface element was absent (i.e. its <code
- title="dom-BarProp-visible">visible</code> attribute may return
- false).</dd>
+ after the document, as appropriate for the user's media. If the
+ user agent has no such user interface element, then the object may
+ act as if the corresponding user interface element was absent
+ (i.e. its <code title="dom-BarProp-visible">visible</code>
+ attribute may return false).</dd>
<dt><dfn>The toolbar <code>BarProp</code> object</dfn></dt>
<dd>Represents the user interface element found immediately above
- or before the document, as appropriate for the <span>default
- view</span>'s media. If the user agent has no such user interface
- element, then the object may act as if the corresponding user
- interface element was absent (i.e. its <code
- title="dom-BarProp-visible">visible</code> attribute may return
- false).</dd>
+ or before the document, as appropriate for the user's media. If the
+ user agent has no such user interface element, then the object may
+ act as if the corresponding user interface element was absent
+ (i.e. its <code title="dom-BarProp-visible">visible</code>
+ attribute may return false).</dd>
</dl>
@@ -62843,21 +62809,18 @@ State: &lt;OUTPUT NAME=I>1&lt;/OUTPUT> &lt;INPUT VALUE="Increment" TYPE=BUTTON O
<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
+ is created as part of the above steps, a new <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>, then the <code>Window</code> object 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>Window</code> object must be changed to point to the new
<code>Document</code> instead.</p>
</li>
@@ -63532,9 +63495,9 @@ State: &lt;OUTPUT NAME=I>1&lt;/OUTPUT> &lt;INPUT VALUE="Increment" TYPE=BUTTON O
<span>scroll to the fragment identifier</span>.</p></li>
<li><p>If the entry is <span>an entry with persisted user
- state</span>, the user agent may update aspects of the document
- view, for instance the scroll position or values of form fields,
- that it had previously recorded.</p></li>
+ state</span>, the user agent may update aspects of the document and
+ its rendering, for instance the scroll position or values of form
+ fields, that it had previously recorded.</p></li>
<li>
@@ -71413,7 +71376,7 @@ interface <dfn>NavigatorAbilities</dfn> {
<pre class="idl">interface <dfn>DragEvent</dfn> : <span>MouseEvent</span> {
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 <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-initDragEvent">initDragEvent</span>(in DOMString typeArg, in boolean canBubbleArg, in boolean cancelableArg, in any dummyArg<!-- used to be viewArg, back when we had views -->, 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);
};</pre>
<dl class="domintro">
@@ -71433,7 +71396,8 @@ interface <dfn>NavigatorAbilities</dfn> {
<p>The <dfn
title="dom-DragEvent-initDragEvent"><code>initDragEvent()</code></dfn>
method must initialize the event in a manner analogous to the
- similarly-named method in the DOM Events interfaces. <a
+ similarly-named method in the DOM Events interfaces, except that the
+ <var title="">dummyArg</var> argument must be ignored. <a
href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
<p>The <dfn
@@ -71719,18 +71683,16 @@ interface <dfn>NavigatorAbilities</dfn> {
<div class="impl">
- <p>Whenever the processing model described
- below causes one of these events to be fired, the event fired must
- use the <code>DragEvent</code> interface defined above, must have
- the bubbling and cancelable behaviors given in the table below, and
- must have the context information set up as described after the
- table, with the <code title="dom-UIEvent-view">view</code> attribute
- set to the view with which the user interacted to trigger the
- drag-and-drop event, the <code
- title="dom-UIEvent-detail">detail</code> attribute set to zero, the
- mouse and key attributes set according to the state of the input
- devices as they would be for user interaction events, and the <code
- title="">relatedTarget</code> attribute set to null.</p>
+ <p>Whenever the processing model described below causes one of these
+ events to be fired, the event fired must use the
+ <code>DragEvent</code> interface defined above, must have the
+ bubbling and cancelable behaviors given in the table below, and must
+ have the context information set up as described after the table,
+ with the <code title="dom-UIEvent-detail">detail</code> attribute
+ set to zero, the mouse and key attributes set according to the state
+ of the input devices as they would be for user interaction events,
+ and the <code title="">relatedTarget</code> attribute set to
+ null.</p>
<p>If there is no relevant pointing device, the object must have its
<code title="">screenX</code>, <code title="">screenY</code>, <code
@@ -72580,10 +72542,6 @@ interface <dfn>NavigatorAbilities</dfn> {
model must be followed as described above, irrespective of how many
documents are involved in the operation.</p>
- <!-- should we mention that you shouldn't include the view from the
- source in the events to the target, or is that obvious enough from
- the requirements in the event section above? -->
-
</div>
@@ -95311,8 +95269,8 @@ time:empty { binding: <i title="">time</i>; }</pre>
<p>When an <code>html</code> element's second child element is a
<code>frameset</code> element, the user agent is expected to render
the <code>frameset</code> element as described below across the
- surface of the <span>view</span>, instead of applying the usual CSS
- rendering rules.</p>
+ surface of the viewport, instead of applying the usual CSS rendering
+ rules.</p>
<p>When rendering a <code>frameset</code> on a surface, the user
agent is expected to use the following layout algorithm:</p>
@@ -95728,8 +95686,8 @@ time:empty { binding: <i title="">time</i>; }</pre>
<p>When the user actually <span title="obtain a physical
form">obtains a physical form</span> (or a representation of a
physical form) of a <code>Document</code>, the user agent is
- expected to create a new view with the print media, render the
- result, and the discard the view.</p>
+ expected to create a new rendering of the <code>Document</code> for
+ the print media.</p>
@@ -101956,12 +101914,6 @@ interface <span>HTMLDocument</span> {
Specification</a></cite>, J. Kesselman, J. Robie, M. Champion,
P. Sharpe, V. Apparao, L. Wood. W3C.</dd>
- <dt id="refsDOMVIEWS">[DOMVIEWS]</dt>
- <dd><cite><a
- href="http://www.w3.org/TR/DOM-Level-2-Views/">Document Object
- Model (DOM) Level 2 Views Specification</a></cite>, A. Le Hors, L.
- Cable. W3C.</dd>
-
<dt id="refsE163">[E163]</dt>
<dd><cite>Recommendation E.163 &mdash; Numbering Plan for The International
Telephone Service</cite>, CCITT Blue Book, Fascicle II.2, pp. 128-134, November

0 comments on commit f6f145d

Please sign in to comment.