HTML Standard Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/4948

File a bug

SVNBugCommentTime (UTC)
49489336[Gecko] [Internet Explorer] [Opera] [Webkit] Drop DOM Views support.2010-04-02 05:32
Index: source
===================================================================
--- source	(revision 4947)
+++ source	(revision 4948)
@@ -4993,10 +4993,10 @@
   <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 @@
   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 @@
 
   <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 @@
   <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 @@
   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 @@
      <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 @@
   <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>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>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 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 @@
   // 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 @@
 
    </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 @@
   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,10 +60772,18 @@
   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
   context</span> and its <span title="script's
@@ -60840,15 +60817,6 @@
 
   </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 @@
    <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 @@
 
     <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 @@
    <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 @@
   <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 @@
   <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 @@
 
   <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 @@
   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 @@
   <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 @@
   <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 @@
    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

|