W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

Re: Notifications

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 11 Feb 2010 11:10:28 +1300
Message-ID: <11e306601002101410i73251a58n91a90c34ff3faa56@mail.gmail.com>
To: John Gregg <johnnyg@google.com>
Cc: Henri Sivonen <hsivonen@iki.fi>, Drew Wilson <atwilson@google.com>, Olli@pettay.fi, public-webapps <public-webapps@w3.org>
We ran into this issue when mapping our own browser notifications to
platform notification APIs. For ambient notifications, you can't rely on the
user being able to click on the notification, because the notification might
time out and disappear on its own before the user has had a chance to react,
so there always has to be another way for the user to get the information
and perform the action. So NotifyOSD not supporting actions is an issue of
convenience, not functionality.

So then, if the NotifyOSD designers think their users don't need that
convenience, that's their call. A generic API can offer support for actions
with the understanding that in some cases users won't be able to use them.

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]
Received on Wednesday, 10 February 2010 22:11:01 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:37 GMT