On Thursday, December 12, 2013 1:57 PM, Jonas Sicking wrote:
> On Thu, Dec 12, 2013 at 1:45 PM, Joel Weinberger wrote:
> >> But it would suck if the result is that they create their own form
> >> fields using s and/or contenteditable.
> >
> > That's true, although some things like that are already
On 2013/12/18 7:12, Maciej Stachowiak wrote:
> I also forgot to mention:
> (3) At least some sites believe that consumer finance regulations
> require them to use autocomplete=off. They believe their requirement
> to protect the user's authentication information and prevent it from
> being accessed
On Wed, Dec 18, 2013 at 8:09 AM, Jonathan Bond-Caron <
jbo...@gdesolutions.com> wrote:
> > On the other hand, if all browsers collectively chose to completely
> > ignore autocomplete=off, that might allow proceeding more
> > aggressively.
> > Sure, and that's why we're bringing it up with th
> On the other hand, if all browsers collectively chose to completely
> ignore autocomplete=off, that might allow proceeding more
> aggressively.
> Sure, and that's why we're bringing it up with the
> standards body. Before we proceed any further, we want to make sure that
> (a) our intention
On Tue, Dec 17, 2013 at 2:12 PM, Maciej Stachowiak wrote:
>
> On Dec 17, 2013, at 11:21 AM, Joel Weinberger wrote:
>
> Thanks for the feedback, everyone. A few people at this point have
> suggested emailing the wha...@whatwg.org list since this is really an
> HTML feature; I'll do that in a few.
On Dec 17, 2013, at 11:21 AM, Joel Weinberger wrote:
> Thanks for the feedback, everyone. A few people at this point have suggested
> emailing the wha...@whatwg.org list since this is really an HTML feature;
> I'll do that in a few. In response to Ian's question, I'm referring to the W3
> Web
On Tue, 17 Dec 2013, Joel Weinberger wrote:
>
> Thanks for the feedback, everyone. A few people at this point have
> suggested emailing the wha...@whatwg.org list since this is really an
> HTML feature; I'll do that in a few. In response to Ian's question, I'm
> referring to the W3 WebForms stan
Thanks for the feedback, everyone. A few people at this point have
suggested emailing the wha...@whatwg.org list since this is really an HTML
feature; I'll do that in a few. In response to Ian's question, I'm
referring to the W3 WebForms standard:
http://www.w3.org/Submission/web-forms2/#the-autoco
On Thu, 12 Dec 2013, Joel Weinberger wrote:
>
> This is a feature (or anti-feature, depending on your perspective :-)
> that has been touted as "good security" for quite some time (in fact,
> the W3C spec specifically calls it out in that regard).
Which spec are we talking about here?
--
Ian H
On Dec 12, 2013, at 11:20 AM, Joel Weinberger wrote:
> Hi all. For a while now, we have wanted on Chrome to ignore
> autocomplete='off' for password fields for the password manager. We believe
> that the current respect for autocomplete='off' for passwords is, in fact,
> harming the security
On Thu, Dec 12, 2013 at 2:03 PM, Joel Weinberger wrote:
> On Thu, Dec 12, 2013 at 1:57 PM, Jonas Sicking wrote:
>> On Thu, Dec 12, 2013 at 1:45 PM, Joel Weinberger wrote:
>> >> But it would suck if the result is that they create their own form
>> >> fields using s and/or contenteditable.
>> >
>>
On Thu, Dec 12, 2013 at 1:57 PM, Jonas Sicking wrote:
> On Thu, Dec 12, 2013 at 1:45 PM, Joel Weinberger wrote:
> >> But it would suck if the result is that they create their own form
> >> fields using s and/or contenteditable.
> >
> > That's true, although some things like that are already pret
On Thu, Dec 12, 2013 at 1:45 PM, Joel Weinberger wrote:
>> But it would suck if the result is that they create their own form
>> fields using s and/or contenteditable.
>
> That's true, although some things like that are already pretty prevalent so
> we've come up with decent heuristics for detecti
On Thu, Dec 12, 2013 at 1:21 PM, Jonas Sicking wrote:
> On Dec 12, 2013 11:21 AM, "Joel Weinberger" wrote:
> > What are this group's thoughts on this? Any particular concerns with
> this approach?
>
> I like the approach.
>
Awesome, and thanks for this feedback :-)
>
> The issue in the past has
On Dec 12, 2013 11:21 AM, "Joel Weinberger" wrote:
> What are this group's thoughts on this? Any particular concerns with this
> approach?
I like the approach.
The issue in the past has been that banks were extremely worried about
the formfill feature in browsers. To the extent that they would
15 matches
Mail list logo
