Open bboyle opened 11 years ago
Handle browsers that support validation API but do not support date input. e.g. Firefox 14
Cannot edit .validity
ValidityState object to set .typeMismatch
to false
on bad date input.
Can replace .checkValidity()
method with custom function (but should use native where possible).
Use custom validity?
Does using custom validity belong in the polyfill file or should it be moved to another script?
initial support for
type="date"
(not datetime, time, month or week—they will be implemented later as needed)will not set
@value
toYYYY-mm-dd
format. Applications must handle input in varied format as iftype="date"
was not supported (fallback in browsers istype="text"
)will accept any value that can be parsed using
new Date( _value_ )
and will polyfill supportYYYY-mm-dd
formats if not natively supported by the javascript engine.add
.valueAsDate
which will be a javascript date object. Will be updatedonchange
http://www.whatwg.org/specs/web-apps/current-work/multipage//common-input-element-attributes.html#dom-input-valueasdateadd
valueAsNumber
as an alias forvalueAsDate.getTime()