Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TimepickerField reacts unexpected to Cut, Backspace and Delete Events #327

Open
marie230 opened this issue Apr 22, 2020 · 3 comments
Open
Labels
in progress started implementation

Comments

@marie230
Copy link

Hi Team,
the Timepicker-Field does not change it's value when Cut, Backspace and Delete events take place.
If a value gets deleted the first time, the default value (instead of the shown input value) is published. If the value gets deleted a second time, there is no update of the value at all. The timepicker itself shows 'HH:MM' in the second case. I would expect that there would either be an update of the time to the default value or a null /undefined value.
The shown value should always be represented in the published value.

I implemented the TimepickerField like this:

        <ngx-timepicker-field 
                              [controlOnly]="true"
                              [format]="24"
                              [defaultTime]="defaultTime"
                              formControlName="time">
        </ngx-timepicker-field>
@Sri-harsha99
Copy link

Did you find any solutions related to it ?

@Sri-harsha99
Copy link

Sri-harsha99 commented Nov 19, 2020

Found a work around. You can use keyboard event to get the value manually and use it.

@Agranom Agranom added the in progress started implementation label Jun 28, 2023
@atanudev2001
Copy link

Hi, I am also facing this issue. so have anybody found any solution to this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in progress started implementation
Projects
None yet
Development

No branches or pull requests

4 participants