On Wed, Nov 21, 2012 at 5:11 PM, Nils Dagsson Moskopp <
n...@dieweltistgarnichtso.net> wrote:
> The proper solution is to let people vote with their wallet for devices
> that are perceived as making input easier – not to hand over power to
> site users making it easier to sniff data.
>
This conta
Nils Dagsson Moskopp schrieb am Thu, 22
Nov 2012 02:11:38 +0100:
> […]
> The proper solution is to let people vote with their wallet for
> devices that are perceived as making input easier – not to hand over
> power to site users making it easier to sniff data.
s/users/owners/g ☺
--
Nils Dags
Peter Kasting schrieb am Wed, 21 Nov 2012
12:04:56 -0800:
> […]
>
> On the contrary, as a user I find that case extremely compelling.
> Maybe I'm too easily frustrated, but it's intensely annoying when I
> have to fill out all my personal information yet again just because
> I've gone to some new
On Wed, Nov 21, 2012 at 9:00 AM, Mounir Lamouri wrote:
> I feel like the real use case is when a user wants to make custom with a
> web site for the first time. It might be indeed harder to get a good
> transformation ration if the user has to write all those information.
> However, I doubt we sh
On 11/11/12 13:26, Charles McCathie Nevile wrote:
> On Sun, 11 Nov 2012 07:50:48 +0100, Maciej Stachowiak
> wrote:
>> (1) If this API fills in a form completely based on stored data, and
>> not by completing the user's typing, then it is "autofill" rather than
>> "autocomplete".
>
> Yep.
>
>> (2
On Sat, Nov 10, 2012 at 10:50 PM, Maciej Stachowiak wrote:
>
> (1) If this API fills in a form completely based on stored data, and not
> by completing the user's typing, then it is "autofill" rather than
> "autocomplete".
>
Yes, we considered requestAutofill() but it seems rather confusing sinc
On Sun, 11 Nov 2012 07:50:48 +0100, Maciej Stachowiak
wrote:
The key questions. I've added some more comments...
(1) If this API fills in a form completely based on stored data, and not
by completing the user's typing, then it is "autofill" rather than
"autocomplete".
Yep.
(2) If this
(1) If this API fills in a form completely based on stored data, and not by
completing the user's typing, then it is "autofill" rather than "autocomplete".
(2) If this API provides the ability to get user information without even
having a visible form, then it's not clear that it is even really
On Fri, Oct 26, 2012 at 3:09 AM, Anne van Kesteren wrote:
> On Fri, Oct 26, 2012 at 10:01 AM, Adam Barth wrote:
> > When should the UA offer to fill in the form (e.g., to select which
> > address they would like to use for shipping this particular order)?
>
> Presumably on page load.
>
>
It was
On Fri, Oct 26, 2012 at 12:43 AM, Anne van Kesteren wrote:
> On Fri, Oct 26, 2012 at 9:24 AM, Elliott Sprehn wrote:
>> [...]
>
> I'm missing the scenario that requires such interference from a web
> developer. Can't a UA just offer to autocomplete a form for me once it
> finds one? (Or in other w
On Fri, Oct 26, 2012 at 10:01 AM, Adam Barth wrote:
> When should the UA offer to fill in the form (e.g., to select which
> address they would like to use for shipping this particular order)?
Presumably on page load.
> In particular, Elliott wrote:
>
>> Authors can also display
>> no forms at a
On Fri, Oct 26, 2012 at 12:43 AM, Anne van Kesteren wrote:
> On Fri, Oct 26, 2012 at 9:24 AM, Elliott Sprehn wrote:
>> [...]
>
> I'm missing the scenario that requires such interference from a web
> developer. Can't a UA just offer to autocomplete a form for me once it
> finds one? (Or in other w
On Fri, Oct 26, 2012 at 9:24 AM, Elliott Sprehn wrote:
> [...]
I'm missing the scenario that requires such interference from a web
developer. Can't a UA just offer to autocomplete a form for me once it
finds one? (Or in other words, unless I'm missing something this seems
like a solution without
13 matches
Mail list logo
