Skip to content
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

Possible DOM update issue with input type="range" #2325

Closed
ttntm opened this issue Oct 7, 2020 · 1 comment
Closed

Possible DOM update issue with input type="range" #2325

ttntm opened this issue Oct 7, 2020 · 1 comment
Labels
has workaround A workaround has been found to avoid the problem 🐞 bug Something isn't working scope: v-model

Comments

@ttntm
Copy link

ttntm commented Oct 7, 2020

Version

3.0.0

Reproduction link

https://codesandbox.io/s/range-slider-issue-2hmjd

Steps to reproduce

  1. click “Show Modal” button
  2. type something into input
  3. see range slider jumping = correcting itself

What is expected?

Render/first tick displays range value correctly.

What is actually happening?

Range slider is jumping = correcting itself when onMounted produces the next tick.


See https://forum.vuejs.org/t/range-input-virtual-dom-update-sequence/104705 for further details and assumptions that could be hepful.

@posva
Copy link
Member

posva commented Oct 7, 2020

We fixed this problem on Vue 2, so it makes sense to have it as well. I suppose min, max, and step have to be set before the value

@posva posva added 🐞 bug Something isn't working scope: v-model has workaround A workaround has been found to avoid the problem labels Oct 7, 2020
yyx990803 added a commit that referenced this issue Jul 21, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Nov 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
has workaround A workaround has been found to avoid the problem 🐞 bug Something isn't working scope: v-model
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants