-
-
Notifications
You must be signed in to change notification settings - Fork 9k
Closed
Labels
❗ p4-importantPriority 4: this fixes bugs that violate documented behavior, or significantly improves perf.Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.🐞 bugSomething isn't workingSomething isn't workingscope: custom elements
Description
Vue version
3.4.28+
Link to minimal reproduction
https://stackblitz.com/edit/vpo3zh?file=src%2Fcomponents%2FExample.vue
Steps to reproduce
Ionic Framework has a ion-range that can be set for dual knobs by passing a string object to the value.
- Make sure to use Vue 3.4.28+
- Navigate to the repro to see the dual knobs of
ion-range. - Notice that the first knob has a value of 20 and the second knob has a value of 80.
- The knobs render as a value of 0
What is expected?
I expect that the knobs render at the correct values. The correct render can be viewed at this additional repro that has Vue 3.4.27.
What is actually happening?
It seems that Vue 3.4.28+ is not passing the string object. It converts it to a NaN instead which leads to the knobs rendering at the 0 position. This is happening when ion-range is using dual knobs. However, no issues are found when downgrading to Vue 3.4.27.
System Info
System:
OS: Linux 5.0 undefined
CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 0 Bytes / 0 Bytes
Shell: 1.0 - /bin/jsh
Binaries:
Node: 18.20.3 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.2.3 - /usr/local/bin/npm
pnpm: 8.15.6 - /usr/local/bin/pnpm
npmPackages:
vue: ^3.4.28 => 3.4.28Any additional comments?
We noticed this bug after a CI check failed. There hasn't been any changes to the ion-range since last month. The only thing that has changed was a patch release from Vue.
sean-perkins, liamdebeasi and alcalyn
Metadata
Metadata
Assignees
Labels
❗ p4-importantPriority 4: this fixes bugs that violate documented behavior, or significantly improves perf.Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.🐞 bugSomething isn't workingSomething isn't workingscope: custom elements