Re: [whatwg] Various autocomplete="" topics

a when inputs are in a ), and possibly better accessibility(?). I've been thinking about cases where we could detect the pattern of fake forms (using text s and s with click handlers together without a ) and provide notices in developer tools to help evangelize but it's looking to be tricky. -- Matthew Noorenberghe

[whatwg] @autocomplete sections

is worth the complexity this adds. How are other UAs planning on supporting multiple arbitrary sections? I'd like to hear more of an argument supporting this feature before implementing it. Is this something that others intend to implement? Thanks, Matthew Noorenberghe [1] http:/

Re: [whatwg] @autocomplete sections

- Original Message - > From: "Ilya Sherman" > To: whatwg@lists.whatwg.org > Sent: Wednesday, May 14, 2014 2:33:58 PM > Subject: Re: [whatwg] @autocomplete sections > > That's a good question. Initially, sections were motivated by the desire > to distinguish between "shipping" and "billin

Re: [whatwg] @autocomplete sections

- Original Message - > On Wed, May 14, 2014 at 6:59 PM, Matthew Noorenberghe < > mattn+wha...@mozilla.com> wrote: > > IMO it makes sense to ignore section-* tokens for rAc for now. I don't > think we need to add "home", "work", and other su

[whatwg] Missing HTMLSelectElement.autocomplete

Hello, Is it intentional that there is no HTMLSelectElement.autocomplete IDL attribute[1]? Both [2] and [3] have it so there is currently inconsistency. Thanks, Matthew Noorenberghe [1] http://www.whatwg.org/specs/web-apps/current-work/#the-select-element [2] http://www.whatwg.org/specs/web

Re: [whatwg] Missing HTMLSelectElement.autocomplete

ust mirroring the attribute content so it adds some value over getAttribute. Matthew Noorenberghe

Re: [whatwg] apple-touch-icon

knowledge… Well-known locations such as /favicon.ico also have the advantage that they work for non-document resources (e.g. PDF, audio or video). Matthew Noorenberghe