Replace date picker for entities card

[thomasloven]

Proposed change

Type of change

Use the vaadin-date-picker we already have for input_datetime in the entities card too.
I made a wrapper to make is ISO compliant and change the formating a bit so it looks more like the paper-input used for time inputs.

I also replaced the date picker in the more-info dialog with the wrapped version.

Finally fixes #4866.

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes Date Picker Display Issues on Chrome (Windows 10) #4866
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[bramkragten]

We should show the date in the format of the user language, we have functions for that: https://github.com/home-assistant/frontend/blob/dev/src/common/datetime/format_date.ts#L4

[bramkragten]

Something like formatDateShort(new Date(d.year, d.month, d.day), this.hass.language)

[bramkragten]

Styling in dark mode is wrong:

[bramkragten]

And can someone remind me why we can't use <input type="date">?

[KTibow]

Maybe because it might look old or bad on some devices? Also not everything supports it.

[zsarnett]

Fing safari man

[bramkragten]

Fuck safari, let them have text inputs 😛 but then we can't parse that to a date object because safari only accepts ISO 8601 strings....

[zsarnett]

I don't understand why they have to make literally everything so Difficult

[bramkragten]

It's weird that we don't have a localDateStringToDate function...

[thomasloven]

Theming has been fixed.

Parsing date strings according to locale seems way harder than you'd think at first glance. Especially since we allow several formats for this; DD, MM-DD, YY-MM-DD and YYYY-MM-DD.
Then there's the order, separators, pre- and postfixes to keep track of. And that's just for those that use the Julian calendar...

[thomasloven]

There's still an annoying 5 px difference in alignment between date and time numbers, but I didn't want to ugly-hack it away, and anything better would require getting more vaadin stuff imported - which I believe we try to avoid? The date picker is used here because we already had it anyway.