Logic issue with datetime field

[Sonya*]

There are logic issues on the datetime field.

If you have the last day of the month and click on arrow up, you will not get to the next day (the first day of the next month). The behavior in the screenshot above is:

• arrow up -> 31.11.2019 (this day does not exist)

Another example:

• arrow up -> 01.10.2019 (should be 01.11.2019)

[bfarber]

What browser are you using? That's generally a function of your browser, unless it does not support date fields at all, in which case we use a polyfill (which we did not develop in-house) to add date management to date fields.

[aia]

This is how chromium-based browsers work. You need to select month or year if you want to change them with this arrows.

[Sonya*]

Just now, bfarber

What browser are you using? That's generally a function of your browser, unless it does not support date fields at all, in which case we use a polyfill (which we did not develop in-house) to add date management to date fields.

Yes, it is Chrome 😪

[Sonya*]

10 hours ago, Mr 13 said:

This is how chromium-based browsers work. You need to select month or year if you want to change them with this arrows.

It does not work for me at all. The month and year are selected in my screenshot. If I open calendar and select the date there, the arrow still does not work properly. In what browser does it work? Is there a possibility to change the field suite-wide? 

[aia]

5 hours ago, Sonya* said:

The month and year are selected in my screenshot.

• They are not selected on your screenshot. 
• You cant select month and year. You can select just one of them, and then use arrows.

This is how it looks when you select one of them:

[Sonya*]

Oh, I see. This is not really user-friendly. 😞 

[bfarber]

On 11/16/2019 at 2:47 AM, Sonya* said:

Oh, I see. This is not really user-friendly. 😞 

You may wish to reach out to the Chromium project (the backbone for Chrome, Safari and soon MS Edge) to relay your feedback. We don't develop the browser itself as I'm sure you are aware. 😛 

[Sonya*]

Thank you! I have checked the docs https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local It is indeed an issue with datetime field there. I will see how I can customize the field myself to get the best user experience.

[Daniel F]

You could hide it 🙂 

input[type=date]::-webkit-inner-spin-button,
input[type=date]::-webkit-outer-spin-button {
  -webkit-appearance: none;
}