[Bug Report] onChange for timePicker

[pwildschut]

What problem does this feature solve?

In the case that a variable change is a trigger for other functionality the onInput event generates too much noise. An onChange event would be more reliable

What is your proposed solution?

I have seen in the code that the timePicker is prepared to return the onchange event. it just seems to be returning the input value, so its actually not doing anything :/

[jacekkarczmarczyk]

@pwildschut Can you provide a codepen with explanation what and when should happen?

[pwildschut]

I have created this to visualize, somehow it looks weird. But functionally it proves my point.

https://codepen.io/pwildschut/pen/aRVJaN

Apologies for the delayed answer.

[KaelWD]

It always emits 00:25 for me, I'd call this a bug.

[jacekkarczmarczyk]

It works better if you use v-model, but maybe this behaviour could be fixed too