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

Re: Allow ... centralized dialog up front

From: Florian Bösch <pyalot@gmail.com>
Date: Fri, 1 Feb 2013 14:37:08 +0100
Message-ID: <CAOK8ODja2zO_r+dYovcak9Gqe_dpcP9J1wGAFyJvStyPDSub9w@mail.gmail.com>
To: Charles McCathie Nevile <chaals@yandex-team.ru>
Cc: Arthur Barstow <art.barstow@nokia.com>, Webapps WG <public-webapps@w3.org>
On Fri, Feb 1, 2013 at 2:29 PM, Charles McCathie Nevile <
chaals@yandex-team.ru> wrote:

> **
> Right now vendors look at a page and can often heurisitically generate a
> permission request that is either consolidated, or depends on actual usage.
>
A heuristic is fine but, it only goes so far. First of all the incidence of
APIs with restricted use is climbing (due to the ever present fetish of
preventing fingerprinting and other security hazards). And second, the
heuristic can only capture APIs that would be simultaneously initiated
(like pointerlock and fullscreen). Sometimes the necessity of an API (clear
at page start) and the actual use (considerably later) do give a heuristic
no chance.


>  One of the patterns clear with Android apps (which use a central dialogue
> like you are proposing) is applications that request a massive number of
> permissions that are irrelevant to their main purpose, and which
> effectively train users to ignore the whole question and click yes. :(
>
And popups solve that problem how? What exactly makes a user less inclined
to just madly mash "yes yes yes" to a series of poups?
Received on Friday, 1 February 2013 13:37:36 GMT

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