[whatwg] Notification API

Drew Wilson atwilson at google.com
Wed Feb 3 13:09:22 PST 2010

BTW, I would highly recommend that we move this conversation to the
public-webapps list. I'm not sure about the best way to do this other than
to stop posting here, starting...um...right after my reply :)

Anyhow, your question below outlines is why there are two exposed
notification APIs - one is simple, lowest-common-denominator text + icon
notifications (createNotification()), and the other is HTML
(createHTMLNotification()). Platforms (such as mobile devices) that can't
support popup HTML notifications can just not expose the
createHTMLNotification attribute. Likewise, if the user on a given system
just wants to force everyone to use text + icon notifications because he
finds the mix of (say) Growl and HTML notifications jarring, then the UA
could provide an option for that (which would cause the UA to not expose the
createHTMLNotification attribute).


On Wed, Feb 3, 2010 at 12:27 PM, Robert O'Callahan <robert at ocallahan.org>wrote:

> On Thu, Feb 4, 2010 at 6:17 AM, John Gregg <johnnyg at google.com> wrote:
>> The Webapps WG is working on a spec for a Web Notification API.  You can
>> see the current draft at
>> http://dev.w3.org/2006/webapi/WebNotifications/publish/, and I would
>> suggest sending comments to the public-webapps mailing list.
>> 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.
>> 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.
> If the underlying platform notification system (e.g. Growl or
> libnotification) doesn't support that functionality, how should the UA
> behave?
> 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.
> Rob
> --
> "He was pierced for our transgressions, he was crushed for our iniquities;
> the punishment that brought us peace was upon him, and by his wounds we are
> healed. We all, like sheep, have gone astray, each of us has turned to his
> own way; and the LORD has laid on him the iniquity of us all." [Isaiah
> 53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100203/3eb0ce3c/attachment-0002.htm>

More information about the whatwg mailing list