<div class="gmail_quote">On Wed, Feb 3, 2010 at 12:27 PM, Robert O'Callahan <span dir="ltr"><<a href="mailto:robert@ocallahan.org">robert@ocallahan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Feb 4, 2010 at 6:17 AM, John Gregg <span dir="ltr"><<a href="mailto:johnnyg@google.com" target="_blank">johnnyg@google.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
The Webapps WG is working on a spec for a Web Notification API. You can see the current draft at <a href="http://dev.w3.org/2006/webapi/WebNotifications/publish/" target="_blank">http://dev.w3.org/2006/webapi/WebNotifications/publish/</a>, and I would suggest sending comments to the public-webapps mailing list.<div>
<br></div><div>That spec attempts to address the icon+title+text use case, and allows a user agent to use a third party presentation system as long as that system can notify of notifications being acknowledged, but also allows HTML as an option if the device supports it. </div>
<div><br></div><div>I disagree with the claim that HTML notifications are overkill as long as they can be done securely, it opens up a lot of benefit to have dynamic & interactive notifications. Even for the simple case of Calendar reminders which might have multiple forms of acknowledgement: snooze for N minutes (a <select> would be nice), or dismiss.</div>
</blockquote><div> </div></div></div>If the underlying platform notification system (e.g. Growl or libnotification) doesn't support that functionality, how should the UA behave?<br><br>I suppose the UA could distinguish between notifications that can be supported by the platform and those that can't, and use the platform notification system when possible, otherwise fall back to its own notifications, but that could be a jarring user experience.<br>
<br></blockquote><div><br></div><div>The spec states that HTML is an optional part of the implementation. If the UA intends to use a presentation system that doesn't support HTML it should not expose the HTML API and just expose the plain one. This isn't ideal as it requires authors to check the capabilities of the UA, but it does provide consistency for the user.</div>
<div><br></div><div> -John</div></div>