Re: [whatwg] Improving autocomplete

2012-10-31 Thread Dan Beam
sing "cancel" elsewhere by the way? Fullscreen uses "error" as > suffix for the event type. The experimental implementation [1] has been updated to dispatch an "autocompleteerror" as per convention/your feedback. Dan Beam db...@chromium.org [1] http://bugs.webkit.org/show_bug.cgi?id=100557

Re: [whatwg] Autocomplete and autofill features and feedback thereon

2012-11-21 Thread Dan Beam
> > > Yes: Most websites that support credit card numbers as inputs do not > support bank account numbers. The few websites that do support bank > account numbers use separate fields for these vs. credit card number > inputs. Labeling both fields identically would leave the b

Re: [whatwg] asynchronous JSON.parse

2013-03-07 Thread Dan Beam
;t this precisely what Transferable objects are for? http://www.whatwg.org/specs/web-apps/current-work/multipage/common-dom-interfaces.html#transferable-objects -- Dan Beam db...@chromium.org > I have put together a small test here - warning, this may kill your > browser: >http://y

[whatwg] Supporting more address levels in autocomplete

2014-02-21 Thread Dan Beam
-localityā€¯, we feel this is a more descriptive and general way to tackle additional administrative levels without making false implications about the semantics of the value that is returned. Questions, concerns, or feedback? -- Dan Beam Evan Stade [1] http://en.wikipedia.org/wiki

[whatwg] Proposal: HTMLFormElement#requestAutocomplete() should return a Promise

2014-04-14 Thread Dan Beam
would be passed on fulfillment* and {"reason": } would be passed on rejection. There should be little compatibility risk as requestAutocomplete() currently returns undefined. Thoughts? Concerns? Questions? -- Dan Beam db...@chromium.org * until I think of something

Re: [whatwg] Proposal: HTMLFormElement#requestAutocomplete() should return a Promise

2014-04-15 Thread Dan Beam
On Mon, Apr 14, 2014 at 9:44 PM, Domenic Denicola < dome...@domenicdenicola.com> wrote: > > From: whatwg-boun...@lists.whatwg.org [mailto: whatwg-boun...@lists.whatwg.org] On Behalf Of Dan Beam > > > I propose requestAutocomplete()[1] should return a Promise. This has bee

Re: [whatwg] Proposal: HTMLFormElement#requestAutocomplete() should return a Promise

2014-04-24 Thread Dan Beam
On Wed, Apr 16, 2014 at 6:59 PM, Domenic Denicola < dome...@domenicdenicola.com> wrote: > > From: db...@google.com [mailto:db...@google.com] On Behalf Of Dan Beam > > > So just pass no argument at all (i.e. arguments.length == 0)? I was under the impression some type of v

Re: [whatwg] Missing HTMLSelectElement.autocomplete

2014-06-04 Thread Dan Beam
encourage authors to use getAttribute() instead), but if and have them we should probably be consistent. -- Dan Beam db...@chromium.org > > Thanks, > Matthew Noorenberghe > > [1] http://www.whatwg.org/specs/web-apps/current-work/#the-select-element > [2] http://www.whatwg.org/specs/we

Re: [whatwg] Missing HTMLSelectElement.autocomplete

2014-06-04 Thread Dan Beam
on't worry, your e-mail is in the queue! Requests for features tend to > take a bit longer for me to deal with than simple bug reports, though. > > > On Wed, 4 Jun 2014, Dan Beam wrote: >> >> It'd be nice to avoid more attribute accessors (and encourage authors to