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 value should always be returned
On 4/25/14, 12:06 AM, Dan Beam wrote:
interface AutocompleteError : DOMException {
DOMException isn't an interface as currently proposed.
In general, please check with public-script-coord before minting new
exception types; there's been a lot of discussion on that issue recently.
-Boris
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 value should always be returned (but I'm biased
by blink/v8's current implementation).
It's equivalent, both for
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
been requested since the creation
Hey whatwg@,
I propose requestAutocomplete()[1] should return a Promise. This has been
requested since the creation of this API[2][3] and seems like a natural
fit. Web authors can then call requestAutocomplete() like this:
form.requestAutocomplete().then(function() {
// form.submit() or
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 been
requested since the creation of this API[2][3] and seems like a natural fit.
Web authors can then call
