HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
2597Remove the showNotification() API due to lack of interest from implementors.2008-12-28 06:20
@@ -17116,30 +17116,31 @@ href="?audio">audio&lt;/a> test instead.)&lt;/p></pre>
     title="plugin">plugins</span>, whether using <a
     href="#sandboxPluginEmbed">the <code>embed</code> element</a>, <a
     href="#sandboxPluginObject">the <code>object</code> element</a>,
     <a href="#sandboxPluginApplet">the <code>applet</code>
     element</a>, or through <a
     href="#sandboxPluginNavigate">navigation</a> of a <span>nested
     browsing context</span>.</p>
 
    </dd>
 
-
+<!-- XXX-NOTIFY
    <dt>The <dfn>sandboxed annoyances browsing context flag</dfn></dt>
 
    <dd>
 
     <p>This flag prevents content from <a
     href="#sandboxNotifications">showing notifications</a> outside of
     the <span>nested browsing context</span>.</p>
 
    </dd>
+-->
 
 
    <dt>The <dfn>sandboxed origin browsing context flag</dfn>, unless
    the <code title="attr-iframe-sandbox">sandbox</code> attribute's
    value, when <span title="split a string on spaces">split on
    spaces</span>, is found to have the <dfn
    title="attr-iframe-sandbox-allow-same-origin"><code>allow-same-origin</code></dfn>
    keyword set</dt>
 
    <dd>
@@ -37743,23 +37744,23 @@ interface <dfn>Window</dfn> {
   <span>Database</span> <span title="dom-opendatabase">openDatabase</span>(in DOMString name, in DOMString version, in DOMString displayName, in unsigned long estimatedSize);
 
   // user prompts
   void <span title="dom-alert">alert</span>(in DOMString message);
   boolean <span title="dom-confirm">confirm</span>(in DOMString message);
   DOMString <span title="dom-prompt">prompt</span>(in DOMString message);
   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, in DOMString features);--><!-- XXX-NOTIFY
   void <span title="dom-showNotification">showNotification</span>(in DOMString title, in DOMString subtitle, in DOMString description);
-  void <span title="dom-showNotification">showNotification</span>(in DOMString title, in DOMString subtitle, in DOMString description, in VoidCallback onclick);
+  void <span title="dom-showNotification">showNotification</span>(in DOMString title, in DOMString subtitle, in DOMString description, in VoidCallback onclick);-->
 
   // <span>cross-document messaging</span>
   void <span title="dom-window-postMessage-2">postMessage</span>(in any message, in DOMString targetOrigin);
   void <span title="dom-window-postMessage-3">postMessage</span>(in any message, in <span>MessagePort</span> messagePort, in DOMString targetOrigin);
 
   // <span>event handler DOM attributes</span>
            attribute <span>EventListener</span> <span title="handler-onabort">onabort</span>;
            attribute <span>EventListener</span> <span title="handler-onbeforeunload">onbeforeunload</span>;
            attribute <span>EventListener</span> <span title="handler-onblur">onblur</span>;
            attribute <span>EventListener</span> <span title="handler-onchange">onchange</span>;
@@ -40025,32 +40026,34 @@ JSURL: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t
   title="dom-modalWindow-returnValue"><code>returnValue</code></dfn>
   DOM attribute, on getting, must return the <span>return value</span>
   of its browsing context, and on setting, must set the <span>return
   value</span> to the given new value.</p>
 
   <p class="note">The <code
   title="dom-window-close">window.close()</code> method can be used to
   close the browsing context.</p>
 
 
+<!-- XXX-NOTIFY
   <h4>Notifications</h4>
 
-<!-- v2 feature requests:
+<!- - v2 feature requests:
 
    - ability to snooze a notification so it comes again later
       - shouldn't be on all messages, only those for which it makes
         sense
       - possibly just provide a new argument that takes an array of
         (label, callback) tuples so that sites can implement this
         themselves
+      - full HTML notifications
 
-  -->
+  - ->
 
   <p>Notifications are short, transient messages that bring the user's
   attention to new information, or remind the user of scheduled
   events.</p>
 
   <p>Since notifications can be annoying if abused, this specification
   defines a mechanism that scopes notifications to a site's existing
   rendering area unless the user explicitly indicates that the site
   can be trusted.</p>
 
@@ -40067,38 +40070,38 @@ JSURL: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t
   notification sources. Then, mail.example.org and
   calendar.example.org would both be able to show notifications,
   without the user having to flag them individually.</p>
 
   <p>The <dfn title="dom-showNotification"><code>showNotification(<var
   title="">title</var>, <var title="">subtitle</var>, <var
   title="">description</var>, <var
   title="">onclick</var>)</code></dfn> method, when invoked, must
   cause the user agent to show a notification.</p>
 
-  <p id="sandboxNotifications">If the method was invoked from a <span title="concept-script">script</span>
-  whose <span title="script's browsing context">browsing
-  context</span> has the <span>sandboxed annoyances browsing context
-  flag</span> set, then the notification must be shown within that
-  <span>browsing context</span>. The notification is said to be a
-  <dfn>sandboxed notification</dfn>.</p>
+  <p id="sandboxNotifications">If the method was invoked from a <span
+  title="concept-script">script</span> whose <span title="script's
+  browsing context">browsing context</span> has the <span>sandboxed
+  annoyances browsing context flag</span> set, then the notification
+  must be shown within that <span>browsing context</span>. The
+  notification is said to be a <dfn>sandboxed notification</dfn>.</p>
 
   <p>Otherwise, if the <span>origin</span> of the <span
   title="script's browsing context">browsing context</span> of the
-  <span title="concept-script">script</span> that invoked the method is <em>not</em> flagged as being a
-  <span>trusted notification source</span>, then the notification
-  should be rendered within the <span>top-level browsing
-  context</span> of the <span>script's browsing context</span>. The
-  notification is said to be a <dfn>normal notification</dfn>. User
-  agents should provide a way to set the origin's <span>trusted
-  notification source</span> flag from the notification, so that the
-  user can benefit from notifications even when the user agent is not
-  the active application.</p>
+  <span title="concept-script">script</span> that invoked the method
+  is <em>not</em> flagged as being a <span>trusted notification
+  source</span>, then the notification should be rendered within the
+  <span>top-level browsing context</span> of the <span>script's
+  browsing context</span>. The notification is said to be a
+  <dfn>normal notification</dfn>. User agents should provide a way to
+  set the origin's <span>trusted notification source</span> flag from
+  the notification, so that the user can benefit from notifications
+  even when the user agent is not the active application.</p>
 
   <p>Otherwise, the <span>origin</span> is flagged as a <span>trusted
   notification source</span>, and the notification should be shown
   using the platform conventions for system-wide notifications. The
   notification is said to be a <dfn>trusted notification</dfn>. User
   agents may provide a way to unset the origin's <span>trusted
   notification source</span> flag from within the notification, so as
   to allow users to easily disable notifications from sites that abuse
   the privilege.</p>
 
@@ -40129,29 +40132,31 @@ JSURL: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t
    semi-transparent white-on-grey overlays centered over the
    screen. Other schemes could include simulated ticker tapes, and
    speech-synthesis playback.</p>
 
   </div>
 
   <p>When a <span>normal notification</span> (but not a
   <span>sandboxed notification</span>) is shown, the user agent may
   bring the user's attention to the <span>top-level browsing
   context</span> of the <span title="script's browsing
-  context">browsing context</span> of the <span title="concept-script">script</span> that invoked the
-  method, if that would be useful; but user agents should not use
-  system-wide notification mechanisms to do so.</p>
+  context">browsing context</span> of the <span
+  title="concept-script">script</span> that invoked the method, if
+  that would be useful; but user agents should not use system-wide
+  notification mechanisms to do so.</p>
 
   <p>When a <span>trusted notification</span> is shown, the user agent
   should bring the user's attention to the notification and the <span
   title="script's browsing context">browsing context</span> of the
-  <span title="concept-script">script</span> that invoked the method, as per the platform conventions for
-  attracting the user's attention to applications.</p>
+  <span title="concept-script">script</span> that invoked the method,
+  as per the platform conventions for attracting the user's attention
+  to applications.</p>
 
   <div class="example">
 
    <p>In the case of <span title="normal notification">normal
    notifications</span>, typically the only attention-grabbing device
    that would be employed would be something like flashing the tab's
    caption, or making it bold, or some such.</p>
 
    <p>In addition, in the case of a <span>trusted notification</span>,
    the entire window could flash, or the browser's application icon
@@ -40165,22 +40170,22 @@ JSURL: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t
   <ul>
 
    <li>The <var title="">title</var>, <var title="">subtitle</var>,
    and <var title="">description</var> strings passed to the
    method. They may be truncated or abbreviated if necessary.</li>
 
    <li>The <span title="meta-application-name">application
    name</span>, if available, or else the <span
    title="dom-document-title">document title</span>, of the
    <span>active document</span> of the <span title="script's browsing
-   context">browsing context</span> of the <span title="concept-script">script</span> that invoked the
-   method.</li>
+   context">browsing context</span> of the <span
+   title="concept-script">script</span> that invoked the method.</li>
 
    <li>An icon chosen from the <span title="external resource
    link">external resource links</span> of type <code
    title="rel-icon">icon</code>, if any are available.</li>
 
   </ul>
 
   <p>If a new notification from one <span>browsing context</span> has
   <var title="">title</var>, <var title="">subtitle</var>, and <var
   title="">description</var> strings that are identical to the <var
@@ -40216,20 +40221,21 @@ JSURL: http://ietfreport.isoc.org/all-ids/draft-hoehrmann-javascript-scheme-00.t
   <p>User agents should support user interaction with notifications,
   if and as appropriate given the platform conventions. If a user
   activates a notification, and the <var title="">onclick</var>
   callback argument was present and is not null, then the <span
   title="script's browsing context">browsing context</span> of the
   <span title="concept-script">script</span> of the function given by
   <var title="">onclick</var> should be brought to the user's
   attention, and the <var title="">onclick</var> callback should then
   be invoked.</p>
 
+-->
 
 
   <h3>System state and capabilities</h3>
 
   <p>The <dfn title="dom-navigator"><code>navigator</code></dfn>
   attribute of the <code>Window</code> interface must return an
   instance of the <code>Navigator</code> interface, which represents
   the identity and state of the user agent (the client), and allows
   Web pages to register themselves as potential protocol and content
   handlers:</p>

|