ngx-timepicker-field problem with HH input in 12 hours format

[Esmodeo]

Focus input - backspace to clear hours = no placeholder, but digit 1 appears...
I can't type hours between 2 and 9 in hours field without using arrows or select all in input (only in 12 hours format) http://prntscr.com/pl40zu

[Agranom]

will check

[robert-king]

not sure if this is the same issue or not, but i'm getting "0" instead of "00" - not sure if that's by design or not, not a big issue though.

Thanks for a great library. One more thing - Luxon.js does add some bloat just fyi.

[Agranom]

@robert-king I guess your issue is more relative to #241 this one

[Esmodeo]

@Agranom any chance you will fix problem with hours input in 12h format field?

[Agranom]

Yes, I will. Just need more time for that

[Agranom]

It should be fixed. Update to v5.2.2 and check please

[Dona278]

@Agranom I've the same issue with 24h format and v5.2.2.
If I have a number already set from model or if I have the input placeholder then the first input is taken and formatted (eg. "2" => "02").
I reproduced the issue also in this way:

Initial state: 11:00

Go on hours input with tab or mouse, then press "2"

No other input allowed

Go to the minutes input and return back to the hours (or lose and gain focus), press "2" again;

Digits aren't formatted and now the input field accept another input before formatting, even if I move to another element and then go back.

Same issue with input placeholer as initial state.

[Agranom]

Are you facing this bug on the demo page? Because I cannot reproduce it.

[Dona278]

Yes!

Initial state:

After press "1"

[Agranom]

I see the different bug ) When I press '1' an hour changes to '02' instead of '01'. But not bug with formatting

[Dona278]

Maybe depends on the browser language?
However if you digit '1' and the input shows '02', you can digit also another number for example '2' to get '22:00'?

[Agranom]

Update to v5.2.3 and check pls

[Dona278]

Same issue..

[Agranom]

@Dona278 could you pls describe the bug ?

[AdditionAddict]

Different platform keyboard behaviour of the ngx-timepicker-field:-

iPad

• works well typing '11' results in '11'
• doesn't matter where cursor is if clicking into field
• tabbing into field also works
• keyboard shows letters rather than numbers (possible fix is to put type="tel" on the input)

Windows Desktop (Chrome / Firefox) - same as described by @Dona278

• practically unusable
• typing '11' results in '01' no matter where cursor is or if you tab into hour/minute field
• only way to enter is type '1', back arrow, delete (←), type '1' or to use up/down arrows which is slow

[Agranom]

Did you try on window desktop?

[AdditionAddict]

Did you try on window desktop?

Apologies above was for Windows (post edited to reflect)

[Agranom]

Do you use right side numbers on your keyboard?

[Agranom]

The issue is resolved. Update to the latest version (v.5.4.0).