You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PrimeVue slider turns integer values into floats, even when configured (min, max, step) to only use integer. The issue occurs on both non-range and range sliders. It is reproducable on the primevue playground (see link or attached file). The issue only occurs, when the user clicks on the slider bar, without dragging the handle. The values will then stay floats, even when dragging the handle.
The issues does not occur, when the handle is dragged before clicking on the slider bar.
justomio
changed the title
Range slider yields float values when not dragging handles beforehand
Slider yields float values when not dragging handles beforehand
Feb 14, 2025
Describe the bug
The PrimeVue slider turns integer values into floats, even when configured (min, max, step) to only use integer. The issue occurs on both non-range and range sliders. It is reproducable on the primevue playground (see link or attached file). The issue only occurs, when the user clicks on the slider bar, without dragging the handle. The values will then stay floats, even when dragging the handle.
The issues does not occur, when the handle is dragged before clicking on the slider bar.
Bildschirmaufnahme.2025-02-14.um.15.02.46.mov
vitejs-vite-cwbnvkzy.zip
Pull Request Link
No response
Reason for not contributing a PR
Other Reason
No response
Reproducer
https://stackblitz.com/edit/vitejs-vite-cwbnvkzy?file=src%2FApp.vue
Environment
Symfony 7.2 with VueJS.
But that doesn't seem relevant as this issue also occurs on the playground
Vue version
3.5.13
PrimeVue version
4.2.4
Node version
No response
Browser(s)
Chrome 133.0, Firefox 135.0, Safari 18.3
Steps to reproduce the behavior
This issue doesn't occur, if you drag the handle beforehand!
Expected behavior
The values should stay integers, as long as the slider has been configured as such.
The text was updated successfully, but these errors were encountered: