On Thu, Nov 13, 2014 at 11:42 PM, Roger Hågensen wrote:
> On 2014-11-14 08:02, Evan Stade wrote:
>
>> On Thu, Nov 13, 2014 at 5:17 PM, Roger Hågensen
>> wrote:
>>
>> On 2014-11-13 20:20, Evan Stade wrote:
>>>
>>> Currently this new beha
f".
>>
>> I am curious what other browsers do around autocomplete="off", and if they
>> respect it for address/user profile/credit card type data. Since there's
>> no
>> way to feature detect the browser's behavior, it would be convenient if
>> all
>> browsers agreed on the meaning/value of the attribute.
>>
>> -- Evan Stade
>>
>
On Thu, Nov 13, 2014 at 5:17 PM, Roger Hågensen wrote:
> On 2014-11-13 20:20, Evan Stade wrote:
>
>> Currently this new behavior is available behind a flag. We will soon be
>> inverting the flag, so you have to opt into respecting autocomplete="off".
>>
>
o opt into respecting autocomplete="off".
I am curious what other browsers do around autocomplete="off", and if they
respect it for address/user profile/credit card type data. Since there's no
way to feature detect the browser's behavior, it would be convenient if all
browsers agreed on the meaning/value of the attribute.
-- Evan Stade
Regarding transaction-amount and transaction-currency: is there consensus
that they are useful types? Should the discussion move to a bug? They are
mentioned here[1] but they aren't the main topic of that bug.
[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=25471
-- Evan Stade
On Tue
Dunno if you still wanted answers to these questions, but in order to not
leave you hanging here are my best attempts:
>
>
> On Tue, 4 Mar 2014, Evan Stade wrote:
> >
> > "dependent-locality" and "locality" have a fairly precise meaning in the
> >
arding the rejection argument: requestAutocomplete() can fail in a
> > way that doesn't map intuitively to the current DOMException names (e.g.
> > the invoking has autocomplete="off" or isn't in a frame).
> > Adding new names for these specific failure cate
he likelihood
of a successful transaction.
Conceptually, how the browser /could/ know the balance on the credit cards
is if it pings some remote server to obtain this information, or if it
remembers each card's credit limit (ignoring how much of the limit may have
already been used), etc.
-- Evan Stade
Specifically, Chromium would disable Wallet for transactions over a certain
limit (at the moment, that's $2k, but this business logic is subject to
change). When Wallet is disabled, users can still store/access their data
in Chrome/Chrome Sync.
-- Evan Stade
On Wed, Apr 23, 2014 at 5:
Perhaps now is a more appropriate time for this discussion, given that
requestAutocomplete is now published in the spec (!).
-- Evan Stade
On Mon, Mar 10, 2014 at 1:33 PM, Evan Stade wrote:
> Hi WhatWG.
>
> Currently, requestAutocomplete lets a user agent provide the same user
>
wants to handle
transactions over $2000 differently from transactions under that amount.
Does this seem reasonable?
-- Evan Stade
On Tue, Mar 4, 2014 at 4:52 PM, Qebui Nehebkau <
qebui.nehebkau+wha...@gmail.com> wrote:
> On Tue, Mar 4, 2014 at 11:41 PM, Ian Hickson wrote:
> > I think the arguments you've presented so far suggest "address-levelN"
> for
> > N=1..4, with 4=region and 3=locality, is probably the simplest thing
On Tue, Mar 4, 2014 at 4:39 PM, Ian Hickson wrote:
> On Tue, 4 Mar 2014, Evan Stade wrote:
> > On Tue, Mar 4, 2014 at 3:41 PM, Ian Hickson wrote:
> > > > > > >
> > > > > > >"address-line1" |
> > > > >
On Tue, Mar 4, 2014 at 3:41 PM, Ian Hickson wrote:
> On Tue, 4 Mar 2014, Evan Stade wrote:
> > >
> > > I am not convinced it'd be that big a load (users generally know what
> > > parts of their addresses are required!). But in any case, if we're
>
On Tue, Mar 4, 2014 at 12:18 PM, Ian Hickson wrote:
>
> On Mon, 3 Mar 2014, Evan Stade wrote:
> > > >
> > > > I don't think you can just write a stack of inputs that accepts
> > > > input for any country. The country determines:
> > > &g
On Mon, Mar 3, 2014 at 2:18 PM, Ian Hickson wrote:
> On Mon, 3 Mar 2014, Evan Stade wrote:
> >
> > I'm still confused. The site author has entered bad markup. Is your
> > concern that site authors will be unable to write good markup?
>
> Some will write good
On Mon, Mar 3, 2014 at 10:28 AM, Ian Hickson wrote:
> On Fri, 28 Feb 2014, Evan Stade wrote [slightly edited for correctness]:
> > On Fri, Feb 28, 2014 at 5:47 PM, Ian Hickson wrote
> > [slightly edited for correctness]:
> > >
> > > My concern is th
gt; > stuff to, then all you need is a working postal address. A textarea
> > with, say, name="postal", if used on different pages, would then let the
> > user enter his entire address very simply, after just once typing it.
> >
> > Probably "postal" sho
is doable enough: creating a
block of text suitable to printing on an envelope given tokenized values.
This tackles the problem of how to format an autocompleted address for a
particular country and UI language (i.e. in the user agent has to know how
to do it, but the website doesn't).
-- Evan Stade
[1] https://code.google.com/p/libaddressinput/
19 matches
Mail list logo
