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

Re: Publishing Web Notification Drafts

From: John Gregg <johnnyg@google.com>
Date: Wed, 13 Oct 2010 11:51:24 -0700
Message-ID: <AANLkTinYzjcXS8-TvQSgp5EhCezCQNQSp0KLETLtfAXe@mail.gmail.com>
To: Doug Turner <dougt@dougt.org>
Cc: Drew Wilson <atwilson@google.com>, Anne van Kesteren <annevk@opera.com>, Web Notification WG <public-web-notification@w3.org>
>> 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

I like this idea too, but left it off for now because the semantics
are trickier than the simple version, and needs further discussion.

Should the user agent be required to present it as a package for
approval (all or nothing, like an extension installation), or allow
the user to choose a subset?  It might be helpful to come up with some
use cases as well.

Received on Wednesday, 13 October 2010 18:51:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:13 UTC