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
QDate emits input only for year and month if the model is not null #7840
Comments
@chaosKP It looks |
Instead of relying on the emit-immediately prop (which is indeed deprecated), please use the additional buttons. Adding an Ok and a Cancel would be much better. https://quasar.dev/vue-components/date#Example--With-additional-buttons |
Deprecated deosn't mean that it isn't working anymore... only that you shouldn't use it because there is a new/better way. ATM there is no better way (afaik) to recieve a event on month/year change, so this is a clear feature regression from version 1.12.. |
Reopening for later posting a codepen. |
Made a reassessment. Compared to behavior from v1.12.13. You're perfectly right, also on the use case (aka "user shouldn't be able to select a day"). Fixed emit-immediately behavior and even removed the deprecation notice (due to the above). Fix will be available in Quasar v1.14.2. |
Describe the bug
If the model of a QDate is null and a year or month is selected without having selected a day, the input event is not emitted.
Codepen/jsFiddle/Codesandbox (required)
https://jsfiddle.net/13ehpqbL/10/
To Reproduce
Steps to reproduce the behavior:
The left QDate with null as model
The right QDate with a value as model
Expected behavior
Input is trigger on year/month/day selection regardless of the current model state like in version 1.12.13
The text was updated successfully, but these errors were encountered: