On Thu, Jan 31, 2013 at 2:18 PM, Florian Bösch pya...@gmail.com wrote:
I would propose to centralize this and make it an up-front dialog remembered
for a site such that:
That kind of bulk approach does not work. Users don't understand
what's going on. (This has been discussed in the past too, I
On Thu, Jan 31, 2013 at 2:18 PM, Florian Bösch pya...@gmail.com wrote:
I would propose to centralize this and make it an up-front dialog remembered
for a site such that:
That kind of bulk approach does not work. Users don't understand
what's going on.
To what extent are we sure users
You suggest a bulk up front permission dialog doesn't work, whereas pinging
the user at random intervals with a popup does?
On Fri, Feb 1, 2013 at 10:12 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jan 31, 2013 at 2:18 PM, Florian Bösch pya...@gmail.com wrote:
I would propose to
On Fri, 01 Feb 2013 11:48:33 +0100, Hallvord Reiar Michaelsen Steen
hallv...@opera.com wrote:
On Thu, Jan 31, 2013 at 2:18 PM, Florian Bösch pya...@gmail.com wrote:
I would propose to centralize this and make it an up-front dialog
remembered for a site such that:
(Your proposal is
On Fri, Feb 1, 2013 at 12:30 PM, Charles McCathie Nevile
cha...@yandex-team.ru wrote:
That kind of bulk approach does not work. Users don't understand
what's going on.
That's what research shows. To be fair, we've generally presented the
options in ways that are over-technical.
This
On 2/1/13 6:30 AM, ext Charles McCathie Nevile wrote:
Yep. There was some security work done a few years ago specifically
looking at the sort of things that users understood, which recommended
that for security it is helpful to have consistent presentation across
browser UI.
Florian - FYI, I
On Fri, Feb 1, 2013 at 12:56 PM, Arthur Barstow art.bars...@nokia.comwrote:
Web Security Experience, Indicators and Trust: Scope and Use Cases
http://www.w3.org/TR/2008/**NOTE-wsc-usecases-20080306/http://www.w3.org/TR/2008/NOTE-wsc-usecases-20080306/
Yeah, has anybody actually even read
Section 9.4.3 Poor usability of dialog boxes
Desktop software commonly reports problems through modal pop-up dialog
boxes. Such dialog boxes frequently appear during normal software use.
Also, the user is frequently given no reasonable course of action other
than clicking the OK button.
On 2/1/13 2:04 AM, ext Tobie Langel wrote:
On 1/31/13 9:13 AM, Arthur Barstow art.bars...@nokia.com wrote:
As I said during one of the testing breakouts in Lyon, ultimately I
suspect the saying beggars can't be choosy will trump. However, AFAIK,
currently, only one of WebApps' thirty active
On Fri, 01 Feb 2013 12:59:35 +0100, Florian Bösch pya...@gmail.com wrote:On Fri, Feb 1, 2013 at 12:56 PM, Arthur Barstow art.bars...@nokia.com wrote:
Web Security Experience, Indicators and Trust: Scope and Use Cases
http://www.w3.org/TR/2008/NOTE-wsc-usecases-20080306/Yeah, has anybody actually
I don't propose writing into a specification how the dialog would look
like. There does need to be a specification however on the API that
developers can use to indicate an applications desire to use any of the
dozen or so restricted APIs.
On Fri, Feb 1, 2013 at 1:25 PM, Charles McCathie Nevile
More precedent
http://kb.mit.edu/confluence/download/attachments/151094600/android-install.jpg
On Fri, Feb 1, 2013 at 1:39 PM, Florian Bösch pya...@gmail.com wrote:
The idea is to allow vendors to improve their UX (if they're so inclined)
by allowing developers (if they're so inclined) to use
OK, I think I'm getting this now.On Fri, 01 Feb 2013 13:39:34 +0100, Florian Bösch pya...@gmail.com wrote:The idea is to allow vendors to improve their UX (if they're so inclined) by allowing developers (if they're so inclined) to use a central, up front API. For lack of a better term let's dummy
On Fri, Feb 1, 2013 at 2:29 PM, Charles McCathie Nevile
cha...@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
On 1/31/13 3:18 PM, ext Rebecca Hauck wrote:
Yes I submitted a batch of tests from TestTWF some time after the Paris
event.
OK, thanks for this clarification (I just noticed your submissions for
IDB and DOMEvents). Sorry Odin for having missed those!
Since I'm not in the webapps working
On Fri, Feb 1, 2013 at 3:02 PM, Adrienne Porter Felt adriennef...@gmail.com
wrote:
My user research on Android found that people have a hard time connecting
upfront permission requests to the application feature that needs the
permission. This meant that people have no real basis by which to
On Fri, 01 Feb 2013 15:16:04 +0100, Florian Bösch pya...@gmail.com wrote:On Fri, Feb 1, 2013 at 3:02 PM, Adrienne Porter Felt adriennef...@gmail.com wrote:
My user research on Android found that people have a hard timeconnecting upfront permission requests to the application feature that needs
Repetitive permission dialog popups at random UI-flows will not solve the
permission fatique any more than a centralized one does. However a
centralized permission dialog will solve the following things fairly
effectively:
- repeated popup fatique
- extension of trust towards a site regardless of
Dear HTML, Web Apps, and Pointer Events Working Groups:
As you may know, the IndieUI Working Group recently published the First
Public Working Draft of IndieUI: Events technical specification at
http://www.w3.org/TR/2013/WD-indie-ui-events-20130122/
IndieUI defines a way for different user
I think we should give it another try by including it in our UI Events spec. I
like the idea of adding the static queryKeyCap(code) API to Keyboard events. I
wonder about the name though. A key capability doesn't sound right. Are we
querying for a key's locale name? e.g.,
On Fri, Feb 1, 2013 at 8:42 PM, Travis Leithead
travis.leith...@microsoft.com wrote:
A key capability doesn't sound right. Are we querying for a key's
locale name? e.g., queryKeyLocaleName(code)?
Well, the keys locales primary symbol for that keyboard key if the key is
printable. There's
On Fri, Feb 1, 2013 at 11:42 AM, Travis Leithead
travis.leith...@microsoft.com wrote:
I think we should give it another try by including it in our UI Events
spec. I like the idea of adding the static queryKeyCap(code) API to
Keyboard events. I wonder about the name though. A key capability
On 2/1/13 5:52 AM, Arthur Barstow art.bars...@nokia.com wrote:
On 1/31/13 3:18 PM, ext Rebecca Hauck wrote:
Since I'm not in the webapps working group, I had to first get access to
the repository. I was told that that to get write access, I (probably)
had
to join the working group [1].
Yes, it
On 2/1/13 4:23 AM, Arthur Barstow art.bars...@nokia.com wrote:
One of things I wondering about is - after you leave your Fellow
position [BTW, that's totally wicked so congrats on that!], and Robin
has moved on to `greener pastures` and Odin has moved on to be CEO of
Opera - if/when there are
On Fri, Feb 1, 2013 at 3:12 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Thu, Jan 31, 2013 at 2:18 PM, Florian Bösch pya...@gmail.com wrote:
I would propose to centralize this and make it an up-front dialog
remembered
for a site such that:
That kind of bulk approach does not work.
On Fri, 01 Feb 2013 15:29:16 +0100, Florian Bösch pya...@gmail.com wrote:Repetitive permission dialog popups at random UI-flows will not solve the permission fatique any more than a centralized one does. However a centralized permission dialog will solve the following things fairly effectively:
-
26 matches
Mail list logo
