W3C home > Mailing lists > Public > public-web-notification@w3.org > October 2010

Web Notifications: please use public-web-notification [Was: Interacting with notifications]

From: Arthur Barstow <art.barstow@nokia.com>
Date: Mon, 04 Oct 2010 11:57:40 -0400
Message-ID: <4CA9F974.4010603@nokia.com>
To: public-webapps <public-webapps@w3.org>, public-web-notification <public-web-notification@w3.org>, Jimmy Forrester-Fellowes <jimmy@rocketware.org>, John Gregg <johnnyg@google.com>
  Please use the public-web-notification list for the Web Notifications 
spec.

John - I think it would be helpful if you would include a note about 
public-web-notification in the Status of Document section.

-ArtB

-------- Original Message --------
Subject: 	Interacting with notifications
Date: 	Mon, 4 Oct 2010 14:41:20 +0200
From: 	ext Jimmy Forrester-Fellowes <jimmy@rocketware.org>
To: 	public-webapps@w3.org <public-webapps@w3.org>



Hi All,
I've been playing with the webkit notifications API while creating a 
chrome-extension. I wanted to raise my concern that I think 
non-interactive notifications are unintuitive for some/most scenarios. I 
understand that using HTML notifications you can add links/buttons so 
the user can action a notification. I think HTML notifications are a 
really bad idea as they will be inconsistent in both styling and user 
experience.

I suggest that the notification API should allow users to add actions to 
a notification that would consist of a Title & URL. This would leave the 
browser/OS notification system to deal with the styling & 
user-experience of the notification.

I would urge a reconsideration of the API.

All the best,
Jimmy

p..s as an Ubuntu user I'm constantly frustrated by the fact I can't 
click on chat notifications etc (via NotifyOSD)
Received on Monday, 4 October 2010 15:58:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 17 December 2012 14:48:27 GMT