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 resca...@emsai.net 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.
I don't like that browsers
.
-- 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, May
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
UK. Also in a natural-language conversation, if you ask me
:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25472
Thanks!
On Wed, 23 Apr 2014, Brian Nicholson wrote:
On Mon, Mar 10, 2014 at 1:33 PM, Evan Stade wrote:
Currently, requestAutocomplete lets a user agent provide the same user
experience across multiple sites for common data input
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
On Wed, Apr 23, 2014 at 9:13 PM, Evan Stade est
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:02 PM
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 est...@chromium.org wrote:
Hi WhatWG.
Currently, requestAutocomplete lets a user agent provide the same
wants to handle
transactions over $2000 differently from transactions under that amount.
Does this seem reasonable?
-- Evan Stade
On Tue, Mar 4, 2014 at 12:18 PM, Ian Hickson i...@hixie.ch 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:
a) what fields make sense
b) what fields are required
On Tue, Mar 4, 2014 at 3:41 PM, Ian Hickson i...@hixie.ch 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
talking about mom-and-pop stores
On Tue, Mar 4, 2014 at 4:39 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 4 Mar 2014, Evan Stade wrote:
On Tue, Mar 4, 2014 at 3:41 PM, Ian Hickson i...@hixie.ch wrote:
address-line1 |
address-line2 |- street-address
address-line3 |
address-level4
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 i...@hixie.ch 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
On Mon, Mar 3, 2014 at 10:28 AM, Ian Hickson i...@hixie.ch wrote:
On Fri, 28 Feb 2014, Evan Stade wrote [slightly edited for correctness]:
On Fri, Feb 28, 2014 at 5:47 PM, Ian Hickson i...@hixie.ch wrote
[slightly edited for correctness]:
My concern is that authors do something like
On Mon, Mar 3, 2014 at 2:18 PM, Ian Hickson i...@hixie.ch 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 markup, I'm sure.
Our job
postal should be specified so that it relates to a postal
address that is complete for delivery except the recipient name. The
reason is that the name is so often asked separately
On Mon, 24 Feb 2014, Evan Stade wrote:
I agree with this, and plan to propose it separately from the proposal
. 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/
18 matches
Mail list logo
