Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
QInput with type number loses reactivity to the model
See original GitHub issueDescribe the bug
Here, some special characters like e or . mess with the way Quasar handles its model on QInput with type number. It’s hard to explain, you’ll understand better when you see it: https://codepen.io/Louis99/pen/MWgpomo?&editable=true&editors=101
and also, it can happen this way too without the special characters: https://codepen.io/Louis99/pen/yLBMjMq?&editable=true&editors=101
It doesn’t seem like much but I believe it’s the source of other issues I’ve had that stem from this, where the reactivity of the component fails. Any thoughts on this? Thank you
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi Louis,
Please also use the
.numbermodifier with v-model, as in:v-model.number="variable". Otherwise it won’t interpret that as a number but a String.Fix will be available in v1.1.1