HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
49489336[Gecko] [Internet Explorer] [Opera] [Webkit] Drop DOM Views support.2010-04-02 05:32
@@ -4986,24 +4986,24 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   </div>
 
 
   <h4 id="mq">Media queries</h4>
 
   <p>A string is a <dfn>valid media query</dfn> if it matches the
   <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>
 
 
 
 
   <h3>URLs</h3>
 
   <h4>Terminology</h4>
 
   <p>A <dfn>URL</dfn> is a string used to identify a resource.</p>
@@ -7347,20 +7347,21 @@ interface <dfn>HTMLDocument</dfn> {
 
   // <span>dynamic markup insertion</span>
            attribute DOMString <span title="dom-innerHTML">innerHTML</span>;
   <span>HTMLDocument</span> <span title="dom-document-open">open</span>(in optional DOMString type, in optional DOMString replace);
   <span>WindowProxy</span> <span title="dom-document-open">open</span>(in DOMString url, in DOMString name, in DOMString features, in optional boolean replace);
   void <span title="dom-document-close">close</span>();
   void <span title="dom-document-write">write</span>(in DOMString... text);
   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>();
            attribute DOMString <span title="dom-document-designMode">designMode</span>;
   boolean <span title="dom-document-execCommand">execCommand</span>(in DOMString commandId);
   boolean <span title="dom-document-execCommand">execCommand</span>(in DOMString commandId, in boolean showUI);
   boolean <span title="dom-document-execCommand">execCommand</span>(in DOMString commandId, in boolean showUI, in DOMString value);
   boolean <span title="dom-document-queryCommandEnabled">queryCommandEnabled</span>(in DOMString commandId);
   boolean <span title="dom-document-queryCommandIndeterm">queryCommandIndeterm</span>(in DOMString commandId);
   boolean <span title="dom-document-queryCommandState">queryCommandState</span>(in DOMString commandId);
@@ -12262,24 +12263,23 @@ gave me some of the songs they wrote. I love sharing my music.&lt;/p>
 
   <div class="impl">
 
   <p>If the link is a <span title="hyperlink link">hyperlink</span>
   then the <code title="attr-link-media">media</code> attribute is
   purely advisory, and describes for which media the document in
   question was designed.</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 -->
 
   <p class="note">The external resource might have further
   restrictions defined within that limit its applicability. For
   example, a CSS style sheet might have some <code
   title="">@media</code> blocks. This specification does not override
   such further restrictions or requirements.</p><!-- note similar text
   in <style> section -->
 
@@ -13593,25 +13593,25 @@ people expect to have work and what is necessary.
   with unknown parameters must be assumed to be unsupported. The <code
   title="">charset</code> parameter must be treated as an unknown
   parameter for the purpose of comparing <span title="MIME type">MIME
   types</span> here.</p>
 
   </div>
 
   <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">
 
   <p class="note">The styles might be further limited in scope,
   e.g. in CSS with the use of <code title="">@media</code>
   blocks. This specification does not override such further
   restrictions or requirements.</p><!-- note similar text in <link>
   section -->
 
   </div>
@@ -20575,29 +20575,20 @@ interface <dfn>HTMLImageElement</dfn> : <span>HTMLElement</span> {
   the presentation of the image appropriately. It can also stop being
   true, e.g. if the user agent finds, after obtaining the image's
   dimensions, that the image data is actually fatally corrupted.</p>
 
   <p>If the image was not fetched (e.g. because the UA's image support
   is disabled, or because the <code title="attr-img-src">src</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">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
   ignored when determining the image's type and whether it is a valid
   image.</p>
 
   <p class="note">This allows servers to return images with error
   responses, and have them displayed.</p>
 
   <p>The user agents should apply the <span title="Content-Type
@@ -25403,23 +25394,23 @@ interface <dfn>CueRangeCallback</dfn> {
      title="attr-source-type">type</code> attribute whose value, when
      parsed as a <span>MIME type</span> (including any codecs
      described by the <code title="">codecs</code> parameter),
      represents <span>a type that the user agent knows it cannot
      render</span>, then end the <span>synchronous section</span>, and
      jump down to the <i title="">failed</i> step below.</p></li>
 
      <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
      title="">absolute URL</var>.</p></li>
 
      <li><p>End the <span>synchronous section</span>, continuing the
      remaining steps asynchronously.</p></li>
 
      <li><p>Run the <span title="concept-media-load-resource">resource
      fetch algorithm</span> with <var title="">absolute URL</var>. If
@@ -59694,88 +59685,36 @@ _:n2 hcard:adr%20street-address "Avenue Q" ;
   <p>Each <span>browsing context</span> has a corresponding
   <code>WindowProxy</code> object.</p>
 
   <p>A <span>browsing context</span> has a <span>session
   history</span>, which lists the <code>Document</code> objects that
   that <span>browsing context</span> has presented, is presenting, or
   will present. At any time, one <code>Document</code> in each
   <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
   contexts.</p>
 
   <hr>
 
   <p>A <span>browsing context</span> can have a <dfn>creator browsing
   context</dfn>, the <span>browsing context</span> that was
   responsible for its creation. If a <span>browsing context</span> has
@@ -60272,20 +60211,21 @@ _:n2 hcard:adr%20street-address "Avenue Q" ;
 
 
 
   <h3>The <code>Window</code> object</h3>
 
   <pre class="idl">[OverrideBuiltins, ReplaceableNamedProperties] <!-- XXX http://www.w3.org/Bugs/Public/show_bug.cgi?id=8241 -->
 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>;
   readonly attribute <span>UndoManager</span> <span title="dom-undoManager">undoManager</span>;
   <span>Selection</span> <span title="dom-getSelection">getSelection</span>();
   [Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-locationbar">locationbar</span>;
   [Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-menubar">menubar</span>;
   [Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-personalbar">personalbar</span>;
   [Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-scrollbars">scrollbars</span>;
   [Replaceable] readonly attribute <span>BarProp</span> <span title="dom-window-statusbar">statusbar</span>;
@@ -60406,30 +60346,59 @@ interface <dfn>Window</dfn> {
    <dt><var title="">window</var> . <code title="dom-window">window</code></dt>
    <dt><var title="">window</var> . <code title="dom-frames">frames</code></dt>
    <dt><var title="">window</var> . <code title="dom-self">self</code></dt>
 
    <dd>
 
     <p>These attributes all return <var title="">window</var>.</p>
 
    </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">
 
   <p>The <dfn title="dom-window"><code>window</code></dfn>, <dfn
   title="dom-frames"><code>frames</code></dfn>, and <dfn
   title="dom-self"><code>self</code></dfn> IDL attributes must all
   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>
 
 
   <div class="impl">
 
   <h4 id="security-window">Security</h4>
 
   <p id="security-2">User agents must raise a
   <code>SECURITY_ERR</code> exception whenever any of the members of a
   <code>Window</code> object are accessed by scripts whose
@@ -60796,23 +60765,31 @@ interface <dfn>Window</dfn> {
   <div class="impl">
 
   <h4>Garbage collection and browsing contexts</h4>
 
   <p>A <span>browsing context</span> has a strong reference to each of
   its <code>Document</code>s and its <code>WindowProxy</code> object,
   and the user agent itself has a strong reference to its <span
   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
   document">document</span>.</p>
 
   <p>When a <span>browsing context</span> is to <dfn>discard a
   <code>Document</code></dfn>, the user agent must run the following
   steps:</p>
 
@@ -60833,29 +60810,20 @@ interface <dfn>Window</dfn> {
    <li><p><span title="a browsing context is discarded">Discard</span>
    all the <span title="child browsing context">child browsing
    contexts</span> of the <code>Document</code>.</p></li>
 
    <li><p>Lose the strong reference from the <code>Document</code>'s
    <span>browsing context</span> to the
    <code>Document</code>.</p></li>
 
   </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
   worker whose list contains that <code>Document</code>.</p>
 
   <p>When <dfn>a <em><span>browsing context</span></em> is
   discarded</dfn>, the strong reference from the user agent itself to
   the <span>browsing context</span> must be severed, and all the
   <code>Document</code> objects for all the entries in the
   <span>browsing context</span>'s session history must be <span
@@ -60959,36 +60927,34 @@ interface <dfn>Window</dfn> {
    the user's favorite pages, or some similar interface concept.</dd>
 
    <dt><dfn>The scrollbar <code>BarProp</code> object</dfn></dt>
 
    <dd>Represents the user interface element that contains a scrolling
    mechanism, or some similar interface concept.</dd>
 
    <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>
 
   <p>The <dfn
   title="dom-window-locationbar"><code>locationbar</code></dfn>
   attribute must return <span>the location bar <code>BarProp</code>
   object</span>.</p>
 
   <p>The <dfn title="dom-window-menubar"><code>menubar</code></dfn>
   attribute must return <span>the menu bar <code>BarProp</code>
@@ -62836,35 +62802,32 @@ State: &lt;OUTPUT NAME=I>1&lt;/OUTPUT> &lt;INPUT VALUE="Increment" TYPE=BUTTON O
     URL</span>, then any <code>Document</code> created by these steps
     must have its <span title="the document's address">address</span>
     set to that <span>URL</span> instead.</p>
 
     <p class="note">An <span title="override URL">override URL</span>
     is set when <span title="concept-js-deref">dereferencing a
     <code>javascript:</code> URL</span>.</p>
 
     <p><dfn title="create a Document object">Creating a new
     <code>Document</code> object</dfn>: When a <code>Document</code>
-    is created as part of the above steps, a new set of <span
-    title="view">views</span> along with the associated
-    <code>Window</code> object must be created and associated with the
+    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>
 
    <li id="navigate-non-Document">
 
     <p><i>Non-document content</i>: If, given <var
     title="">type</var>, the new resource is to be handled by
     displaying some sort of inline content, e.g. a native rendering of
     the content, an error message because the specified type is not
@@ -63525,23 +63488,23 @@ State: &lt;OUTPUT NAME=I>1&lt;/OUTPUT> &lt;INPUT VALUE="Increment" TYPE=BUTTON O
 
    <li><p>If the traversal was initiated with <dfn>replacement
    enabled</dfn>, remove the entry immediately before the
    <var title="">specified entry</var> in the session history.</p>
 
    <li><p>If the <i>specified entry</i> is not <span>an entry with
    persisted user state</span>, but its URL has a fragment identifier,
    <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>
 
     <p>If the <i>specified entry</i> is a state object or the first
     entry for a <code>Document</code>, the user agent must run the
     following substeps:</p>
 
     <ol>
 
      <li><p>If the entry is a <span>state object</span> entry, let <var
@@ -71406,41 +71369,42 @@ interface <dfn>NavigatorAbilities</dfn> {
 
 
   <h4>The <code>DragEvent</code> and <code>DataTransfer</code> interfaces</h4>
 
   <p>The drag-and-drop processing model involves several events. They
   all use the <code>DragEvent</code> interface.</p>
 
   <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">
 
    <dt><var title="">event</var> . <code title="dom-DragEvent-dataTransfer">dataTransfer</code></dt>
 
    <dd>
 
     <p>Returns the <code>DataTransfer</code> object for the event.</p>
 
    </dd>
 
   </dl>
 
   <div class="impl">
 
   <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
   title="dom-DragEvent-dataTransfer"><code>dataTransfer</code></dfn>
   attribute of the <code>DragEvent</code> interface represents the
   context information for the event.</p>
 
   </div>
 
   <pre class="idl">interface <dfn>DataTransfer</dfn> {
@@ -71712,32 +71676,30 @@ interface <dfn>NavigatorAbilities</dfn> {
   </div>
 
 
   <h4 id="dndevents">Events fired during a drag-and-drop action</h4>
 
   <p>The following events are involved in the drag-and-drop
   model.</p>
 
   <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
   title="">clientX</code>, <code title="">clientY</code>, and <code
   title="">button</code> attributes set to 0.</p>
 
   <!-- interaction event spec point -->
 
   </div>
 
@@ -72573,24 +72535,20 @@ interface <dfn>NavigatorAbilities</dfn> {
 
   <h5>When the drag-and-drop operation starts or ends in another
   document</h5>
 
   <p>The model described above is independent of which
   <code>Document</code> object the nodes involved are from; the events
   must be fired as described above and the rest of the processing
   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>
 
 
 
   <div class="impl">
 
   <h5>When the drag-and-drop operation starts or ends in another
   application</h5>
 
   <p>If the drag is initiated in another application, the <span>source
@@ -95304,22 +95262,22 @@ time:empty { binding: <i title="">time</i>; }</pre>
 
 
 
   <div class="impl">
 
   <h3>Frames and framesets</h3>
 
   <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>
 
   <ol>
 
    <li>
 
     <p>The <var title="">cols</var> and <var title="">rows</var>
     variables are lists of zero or more pairs consisting of a number
@@ -95721,22 +95679,22 @@ time:empty { binding: <i title="">time</i>; }</pre>
 
   <p>User agents are expected to allow the user to request the
   opportunity to <dfn>obtain a physical form</dfn> (or a
   representation of a physical form) of a <code>Document</code>. For
   example, selecting the option to print a page or convert it to PDF
   format.</p>
 
   <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>
 
 
 
   </div>
 
 
 
   <h2 id="obsolete">Obsolete features</h2>
 
   <h3>Obsolete but conforming features</h3>
@@ -101949,26 +101907,20 @@ interface <span>HTMLDocument</span> {
    Object Model (DOM) Level 3 Events Specification</a></cite>,
    D. Schepers. W3C.</dd>
 
    <dt id="refsDOMRANGE">[DOMRANGE]</dt>
    <dd><cite><a
    href="http://www.w3.org/TR/DOM-Level-2-Traversal-Range/">Document
    Object Model (DOM) Level 2 Traversal and Range
    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
    1988.</dd>
 
    <dt id="refsECMA262">[ECMA262]</dt>
    <dd><cite><a
    href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript
    Language Specification</a></cite>. ECMA.</dd>
 

|