search

aurelia / ux

A user experience framework with higher-level capabilities, designed to bring simplicity and elegance to building cross-device, rich experiences.
MIT License
368 stars 55 forks source link

fix(input): pass through date input types, default config #286

Closed MaximBalaganskiy closed 4 years ago

MaximBalaganskiy commented 4 years ago

Returning true is needed to support clicks on a native calendar button.

bigopon commented 4 years ago

I guess there's no reason to not pass this through. Though do we need to handle the value of date-* input differently? always get as Date object or just a string?

MaximBalaganskiy commented 4 years ago

Converting to a date would be convenient but not consistent with the native input. Not sure, personally

bigopon commented 4 years ago

Converting to a date would be convenient but not consistent with the native input. Not sure, personally

we have input.valueAsDate for this, though I've never tried all input/change events combination with different browsers to be sure enough of this either.