Closed diviman closed 1 year ago
Why this happens:
update:model-value
when their new internal value is different from the external value (:model-value
):model-value="lazy"
lazy
model stays the sameSolution:
Hi Dan,
Thank you very much for your brilliant explanation!
I tried to reproduce your solution in my context with some changes aimed to fit this approach to my needs. I found a way how to redesign the logic using your advice. Now it works as was expected.
Sincerely, Olexiy Mudriy.
On Fri, Jan 13, 2023 at 10:48 AM Popescu Dan @.***> wrote:
Closed #15261 https://github.com/quasarframework/quasar/issues/15261 as completed.
— Reply to this email directly, view it on GitHub https://github.com/quasarframework/quasar/issues/15261#event-8218620390, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKQUA75OT24JK2ICV4W6OPTWSEJFBANCNFSM6AAAAAATZYWKY4 . You are receiving this because you authored the thread.Message ID: @.***>
What happened?
When QSlider is used in "lazy" mode with a custom label there is some unexpected component behaviour. If you move the slider to the right-left, then when moving through the initial value, the label does not change. On the contrary, if you do not use customization but the 'lazy' mode still, the label changes its value as expeced.
What did you expect to happen?
The value of the label should be changed in the same way as if you'd moved through the starting value in the "lazy" mode without label customization.
Reproduction URL
https://codepen.io/diviman/pen/XWBgbPj
How to reproduce?
Go to the QSlider component at the bottom and try to pass through p.1 to p.8 described above. You could see that the value of the label changes as expected.
Flavour
Quasar CLI with Webpack (@quasar/cli | @quasar/app-webpack)
Areas
Components (quasar), SPA Mode
Platforms/Browsers
Firefox, Chrome, Safari
Quasar info output
Relevant log output
No response
Additional context
No response