Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/whatwg/html/issues/4770 below:

Unclear why Local Date and Time input type does not support valueAsDate · Issue #4770 · whatwg/html · GitHub

https://html.spec.whatwg.org/multipage/input.html#local-date-and-time-state-(type=datetime-local):concept-input-step-scale

The input type datetime-local does not support setting and getting the value of the input as a Date object, while it does support setting and getting the value as a number (epoch seconds).

// inputElement = <input type="datatime-local">
inputElement.valueAsDate = new Date(someDateString); // DOMException: Failed to set the 'valueAsDate' property on 'HTMLInputElement': This input element does not support Date values.
inputElement.valueAsNumber = new Date(someDateString).valueOf();

This doesn't seem consistent, since the input types date, time, week and month do support both:

// inputElement = <input type="date">
inputElement.valueAsDate = new Date(someDateString);
inputElement.valueAsNumber = new Date(someDateString).valueOf();

I would like to request some information to be added to the spec on why this feature isn't supported by this input type. But ideally I would prefer the following gets added to the spec for the datetime-local input type:

• The algorithm to convert a string to a Date object, given a string input, is as follows: If parsing a date from input results in an error, then return an error; otherwise, return a new Date object representing midnight UTC on the morning of the parsed date.
• The algorithm to convert a Date object to a string, given a Date object input, is as follows: Return a valid date string that represents the date current at the time represented by input without a specified UTC time zone.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4