mention the problem with the permission model used; mention the static attribute problem
authorAnne van Kesteren <annevk@opera.com>
Tue, 12 Jun 2012 09:59:53 +0200
changeset 8 f06ff848e6c0
parent 7 5f2b3a2f7c6c
child 9 13eb4cb483c5
mention the problem with the permission model used; mention the static attribute problem
Overview.html
Overview.src.html
--- a/Overview.html	Tue Jun 12 09:53:32 2012 +0200
+++ b/Overview.html	Tue Jun 12 09:59:53 2012 +0200
@@ -411,6 +411,10 @@
   "rtl"
 };</pre>
 
+<p class="XXX">Web IDL is
+<a href="http://lists.w3.org/Archives/Public/public-script-coord/2012AprJun/0222.html">not yet updated</a>
+to allow for static attributes.
+
 <p>The
 <dfn id="dom-notification" title="dom-Notification"><code>Notification(<var title="">title</var>, <var title="">options</var>)</code></dfn>
 constructor must run these steps:
@@ -482,6 +486,11 @@
  <var title="">permission</var> as single argument.
 </ol>
 
+<p class="warning">In designing the platform notifications are the one
+instance thus far where asking the user upfront makes sense. Specifications
+for other APIs should not use this pattern and instead employ one of the
+<a href="http://robert.ocallahan.org/2011/06/permissions-for-web-applications_30.html">many more suitable alternatives</a>.
+
 <p>The following are the <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#event-handlers">event handlers</a>
 (and their corresponding
 <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/webappapis.html#event-handler-event-type" title="event handler event type">event handler event types</a>)
--- a/Overview.src.html	Tue Jun 12 09:53:32 2012 +0200
+++ b/Overview.src.html	Tue Jun 12 09:59:53 2012 +0200
@@ -389,6 +389,10 @@
   "rtl"
 };</pre>
 
+<p class=XXX>Web IDL is
+<a href="http://lists.w3.org/Archives/Public/public-script-coord/2012AprJun/0222.html">not yet updated</a>
+to allow for static attributes.
+
 <p>The
 <dfn title=dom-Notification><code>Notification(<var title>title</var>, <var title>options</var>)</code></dfn>
 constructor must run these steps:
@@ -460,6 +464,11 @@
  <var title>permission</var> as single argument.
 </ol>
 
+<p class=warning>In designing the platform notifications are the one
+instance thus far where asking the user upfront makes sense. Specifications
+for other APIs should not use this pattern and instead employ one of the
+<a href="http://robert.ocallahan.org/2011/06/permissions-for-web-applications_30.html">many more suitable alternatives</a>.
+
 <p>The following are the <span data-anolis-spec=html>event handlers</span>
 (and their corresponding
 <span data-anolis-spec=html title="event handler event type">event handler event types</span>)