On Mon, May 5, 2014 at 10:38 PM, Matthew Noorenberghe
mattn+wha...@mozilla.com wrote:
On Fri, Apr 11, 2014 at 3:36 PM, Edward O'Connor eocon...@apple.com
wrote:
I actually have a similar problem with purely JS-handled forms even
unrelated to credentials. Because the form is never really
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
On Fri, Apr 11, 2014 at 3:36 PM, Edward O'Connor eocon...@apple.com wrote:
I actually have a similar problem with purely JS-handled forms even
unrelated to credentials. Because the form is never really submitted
(even if we reuse the submit infrastructure, we cancel the 'submit'
event and
On Fri, Apr 25, 2014 at 4:54 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 3 Apr 2014, Mike West wrote:
On Wed, Apr 2, 2014 at 10:56 PM, Ian Hickson i...@hixie.ch wrote:
Also, consider the case of login forms without username fields. You
see this sort of thing a lot these days, when
For the real submission case, I guess what we want is a way to say
autocomplete=off after the fact, basically. An HTTP header seems
like the most obvious solution.
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25239
Again, these need multiple vendors on board to make progress.
Hi,
Ian wrote:
Is there any reason to have two fields here, why not just new both
times?
That works for me. Browsers can supply the same value for multiple
autocomplete=new-password fields in the same form.
Also, should we have an old field for the old password, or is the
lack of an
On Wed, Apr 2, 2014 at 10:56 PM, Ian Hickson i...@hixie.ch wrote:
Also, consider the case of login forms without username fields. You see
this sort of thing a lot these days, when sites remember who was last
logged in:
form
labelPassword for hober: input type=password name=pw/label
[General point, so not quoting anyone in particular]
[Resending to list, apologies to Ian]
Why would you define any address components other than those in vCard, a
standard with massive implementation and interoperable with most address
book applications and services?
--
Andy Mabbett