search

telerik / kendo-angular

Issue tracker - Kendo UI for Angular
http://www.telerik.com/kendo-angular-ui/
Other
467 stars 217 forks source link

Impossible to input certain hour values for certain dates using keyboard entry #1366

Open craigsmitham opened 6 years ago

craigsmitham commented 6 years ago

I'm submitting a.

For certain dates, when using keyboard entry to modify the hour to a time greater than 20 (using HH format), the date input will not update.

Current behavior

  1. Set the date input to any of the problematic dates below
  2. Enter value greater than "20" in the hour segment of the input
  3. The entered value does not update the hour segment of the input

Expected behavior

  1. Set the date input to any of the problematic dates below
  2. Enter value greater than "20" in the hour segment of the input
  3. The entered value should appear in the hour segment of the input

Problematic Dates

Minimal reproduction of the problem with instructions

Environment

Package versions: N/A - reproducible on demo site

Browser:

ggkrustev commented 6 years ago

Hi @craigsmitham, thanks for the detailed report. I tried to replicate the issue locally, but to no avail.

https://www.screencast.com/t/BivlBkj10l

The issue could be reproducible only in particular browser timezone. Could you share the TZ of the browser where you are testing? Also am I missing something applying the repro steps?

craigsmitham commented 6 years ago

@ggkrustev we've been able to reproduce this in both US central and pacific time zones.

We now think the issue has something to do with daylight savings. Any date where daylight savings come into effect this will be an issue.

ggkrustev commented 6 years ago

@craigsmitham, thanks for the clarification.

Indeed, the component will not accept the first typed character - 2, because this will produce a non-existing date - 03/11/2018 02:00. Basically, when a 2 is typed, the component tries to create the aforementioned date, browser adjust the time according DST info and creates 03/11/2018 03:00. Hence any additional character will produce invalid hour (> 24) and will be ignored.

Although the described behavior is somewhat expected, the UX is not great. We will further investigate the case and will post updates while research progresses.

craigsmitham commented 6 years ago

THe HTML5 datetime-local input does not appear to have this issue: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local

ggkrustev commented 6 years ago

Yep, I did check the datetime-local control and noticed that it behaves correctly. As I mentioned, we recognized the defect and will research how to improve the current behavior. Stay tuned for updates.

PlasticLizard commented 5 years ago

Running into this again this year - it's quite surprising for our users - any progress? Thanks! - Nathan

billm23 commented 4 years ago

It's been a couple years, any progress on this?

craigsmitham commented 4 years ago

Any update?