Closed OguzhanAgca closed 2 months ago
The issue here is that the onFocus
method is not exposed when a new version is published, you would need to connect both the onFocus
and onBlur
input events to be able to parse the date with auto-apply
.
I should probably make docs a bit clearer :)
The issue here is that the
onFocus
method is not exposed when a new version is published, you would need to connect both theonFocus
andonBlur
input events to be able to parse the date withauto-apply
.I should probably make docs a bit clearer :)
Thank you for your interest, I will try it when the new version is released. :)
The issue here is that the
onFocus
method is not exposed when a new version is published, you would need to connect both theonFocus
andonBlur
input events to be able to parse the date withauto-apply
.I should probably make docs a bit clearer :)
By "connecting" you mean just using #dp-input="{ value, onInput, onBlur, onFocus }"
and then simply
@input="onInput"
@focus="onFocus"
@blur="onBlur"
Damn, that would be great to have 👍
@Bowske Yes, that is correct
Describe the bug Hello, when we use custom input using slot (
#dp-input
), datepicker's modelValue is not updated. Whether the input used is native or custom input, it does not work very well.I looked through the documentation a lot, but I couldn't find anything regarding this situation. If this is really a bug, I am sharing screenshots below.
Also, I'm not sure, but this problem seems to be present in the example in the documentation. Dp-Input
To Reproduce Steps to reproduce the behavior:
textInput=true
andformat='yyyy-MM-dd'
, it creates a custom input.Expected behavior When we make a change to the custom input, the modelValue in the datepicker should be updated.
Screenshots Screencast from 17-05-2024 13:52:19.webm
Desktop