reports, though.
On Wed, 4 Jun 2014, Dan Beam wrote:
It'd be nice to avoid more attribute accessors (and encourage authors to
use getAttribute() instead), but if input and textarea have them we
should probably be consistent.
Can you elaborate on the cost of attribute accessors?
Namespace
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 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
* and
{reason: matching AutocompleteErrorEvent#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 useful for the success
-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 db...@chromium.org
Evan Stade est...@chromium.org
[1] http
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://yoric.github.com/Bugzilla-832664/
While there are considerable
that do support bank
account numbers use separate fields for these vs. credit card number
inputs. Labeling both fields identically would leave the browser unable to
distinguish which field to fill with what info.
On Wed, 31 Oct 2012, Dan Beam wrote:
The experimental implementation [1] has
.
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
