[html5] r1492 - /

[whatwg at whatwg.org]

Author: ianh
Date: 2008-04-27 15:21:22 -0700 (Sun, 27 Apr 2008)
New Revision: 1492

Modified:
   index
   source
Log:
[e] (0) The features argument of showModalDialog() is ignored. Removing it from the spec.

Modified: index
===================================================================
--- index	2008-04-27 08:59:44 UTC (rev 1491)
+++ index	2008-04-27 22:21:22 UTC (rev 1492)
@@ -26809,8 +26809,8 @@
   DOMString <a href="#prompt" title=dom-prompt>prompt</a>(in DOMString message, in DOMString default);
   void <a href="#print" title=dom-print>print</a>();
   any <a href="#showmodaldialog" title=dom-showModalDialog>showModalDialog</a>(in DOMString url);
-  any <a href="#showmodaldialog" title=dom-showModalDialog>showModalDialog</a>(in DOMString url, in any arguments);
-  any <a href="#showmodaldialog" title=dom-showModalDialog>showModalDialog</a>(in DOMString url, in any arguments, in DOMString features);
+  any <a href="#showmodaldialog" title=dom-showModalDialog>showModalDialog</a>(in DOMString url, in any arguments);<!--
+  any <span title="dom-showModalDialog">showModalDialog</span>(in DOMString url, in any arguments, in DOMString features);-->
 
   // other browsing contexts
   readonly attribute <a href="#window">Window</a> <a href="#frames" title=dom-frames>frames</a>;
@@ -27961,7 +27961,8 @@
 
   <p>The <dfn id=showmodaldialog
    title=dom-showModalDialog><code>showModalDialog(<var title="">url</var>,
-   <var title="">arguments</var>, <var title="">features</var>)</code></dfn>
+   <var title="">arguments</var><!--, <var
+  title="">features</var>-->)</code></dfn>
    method, when invoked, must cause the user agent to run the following
    steps:
 
@@ -49518,11 +49519,8 @@
 > [2] http://www.stopdesign.com/articles/throwing_tables/
 
 
-In other areas, however, the replacement is not a match in terms of functionality. Like it or not, but showModalDialog is a better way to provide feature-rich user feedback windows than window.confirm (which Firefox supports, even though there is NO PUBLIC STANDARD for it). With showModalDialog, I can pop a window offering "Yes," "No," or "Cancel" buttons that requires a response before proceeding. With window.confirm, I have to craft all my questions as something to which "OK" or "Cancel" makes sense, never mind asking for three, four, or five state responses.
-- http://news.zdnet.com/2100-9588-5438955.html ( John Carroll )
 
 
-
 > http://channel9.msdn.com/wiki/default.aspx/Channel9.InternetExplorerFeatureRequests
 >    Alternate way of caching content
 >    Avalon Integration

Modified: source
===================================================================
--- source	2008-04-27 08:59:44 UTC (rev 1491)
+++ source	2008-04-27 22:21:22 UTC (rev 1492)
@@ -24509,8 +24509,8 @@
   DOMString <span title="dom-prompt">prompt</span>(in DOMString message, in DOMString default);
   void <span title="dom-print">print</span>();
   any <span title="dom-showModalDialog">showModalDialog</span>(in DOMString url);
-  any <span title="dom-showModalDialog">showModalDialog</span>(in DOMString url, in any arguments);
-  any <span title="dom-showModalDialog">showModalDialog</span>(in DOMString url, in any arguments, in DOMString features);
+  any <span title="dom-showModalDialog">showModalDialog</span>(in DOMString url, in any arguments);<!--
+  any <span title="dom-showModalDialog">showModalDialog</span>(in DOMString url, in any arguments, in DOMString features);-->
 
   // other browsing contexts
   readonly attribute <span>Window</span> <span title="dom-frames">frames</span>;
@@ -25656,8 +25656,8 @@
   <h4>Dialogs implemented using separate documents</h4>
 
   <p>The <dfn title="dom-showModalDialog"><code>showModalDialog(<var
-  title="">url</var>, <var title="">arguments</var>, <var
-  title="">features</var>)</code></dfn> method, when invoked, must
+  title="">url</var>, <var title="">arguments</var><!--, <var
+  title="">features</var>-->)</code></dfn> method, when invoked, must
   cause the user agent to run the following steps:</p>
 
   <ol>
@@ -44736,11 +44736,8 @@
 > [2] http://www.stopdesign.com/articles/throwing_tables/
 
 
-In other areas, however, the replacement is not a match in terms of functionality. Like it or not, but showModalDialog is a better way to provide feature-rich user feedback windows than window.confirm (which Firefox supports, even though there is NO PUBLIC STANDARD for it). With showModalDialog, I can pop a window offering "Yes," "No," or "Cancel" buttons that requires a response before proceeding. With window.confirm, I have to craft all my questions as something to which "OK" or "Cancel" makes sense, never mind asking for three, four, or five state responses.
-- http://news.zdnet.com/2100-9588-5438955.html ( John Carroll )
 
 
-
 > http://channel9.msdn.com/wiki/default.aspx/Channel9.InternetExplorerFeatureRequests
 >    Alternate way of caching content
 >    Avalon Integration