- From: Doug Turner <dougt@dougt.org>
- Date: Wed, 13 Oct 2010 11:38:36 -0700
- To: Drew Wilson <atwilson@google.com>
- Cc: John Gregg <johnnyg@google.com>, Anne van Kesteren <annevk@opera.com>, Web Notification WG <public-web-notification@w3.org>
On Oct 13, 2010, at 10:15 AM, Drew Wilson wrote: > Overall this looks good. A few comments: > > 1) To address Doug's earlier comment about dropping things like "dir" and "replaceId" - I'd be concerned about omitting these. The use cases around "dir" seem fairly well established, and replaceId likewise seems strongly grounded in use cases and is already supported by some system platforms (I believe growl supports this, no?). I do not think so? [GrowlApplicationBridge notifyWithTitle:(NSString *)title description:(NSString *)description notificationName:(NSString *)notificationName iconData:(NSData *)iconData priority:(signed int)priority isSticky:(BOOL)isSticky clickContext:(id)clickContext] > I'd like our API to be driven by our use cases and requirements, and not by the functionality exposed by any specific current system platform, as the latter may change over time at the whims of various development teams. Maybe. If we add such attributes, they should be optional. > 3) This might be more than we want to bite off right now, but one concern people have had about HTML5's permission model is it requires the developer to request one permission at a time, leading to a sequence of info bars/permission dialogs as the user is serially prompted for things like geolocation access, extra DB quota, notifications, etc. If we are defining a general-purpose permissions API, it might be useful to allow the developer to pass an array of features to requestPermission(), which the user agent could potentially consolidate into a single permission grant UI flow. +1
Received on Wednesday, 13 October 2010 18:39:10 UTC