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

range: track width gets out of sync with input value #157

Closed
4 of 8 tasks
ambar-arkin opened this issue Aug 23, 2022 · 3 comments · Fixed by #158
Closed
4 of 8 tasks

range: track width gets out of sync with input value #157

ambar-arkin opened this issue Aug 23, 2022 · 3 comments · Fixed by #158

Comments

@ambar-arkin
Copy link

Describe the bug

The color/highlight of the range input goes out of sync with the input value when the input value is changed in a controlled input by calling setValue.

How to reproduce

https://stackblitz.com/edit/vitejs-vite-qcpvwl?file=src/App.jsx

Steps to reproduce the behavior:

  1. The range slider is initially at 50/100
  2. Move it to somewhere around 75/100
  3. Click the reset button.
  4. See the colored portion is from 0 to 75 while input value is 50.

image

Expected behavior

The colored portion should change when changing input value using javascript.

Versions

Clarity project:

  • Clarity Core
  • Clarity Angular/UI

Clarity version:

  • v5.x
  • v6.x

Framework:

  • Angular
  • React
  • Vue
  • Other:

Framework version:
React 17, 18

Device:

  • Type: MacBook
  • OS: MacOS Monterey
  • Browser: Chromium
  • Version: 104

Additional notes

Add any other notes about the problem here.

@ashleyryan ashleyryan self-assigned this Aug 23, 2022
@ashleyryan ashleyryan changed the title CdsRange React component colored portion goes out of sync with input value range: track width gets out of sync with input value Aug 23, 2022
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Aug 23, 2022
fixes vmware-clarity#157

the input event doesn't fire when the value is changed in code, so listen for the property change
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Aug 24, 2022
fixes vmware-clarity#157

the input event doesn't fire when the value is changed in code, so listen for the property change
ashleyryan pushed a commit that referenced this issue Aug 24, 2022
fixes #157

the input event doesn't fire when the value is changed in code, so listen for the property change
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Aug 24, 2022
fixes vmware-clarity#157

the input event doesn't fire when the value is changed in code, so listen for the property change
ashleyryan pushed a commit that referenced this issue Aug 24, 2022
fixes #157

the input event doesn't fire when the value is changed in code, so listen for the property change
@github-actions
Copy link

🎉 This issue has been resolved in version 5.8.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This issue has been resolved in version 6.1.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

Hi there 👋, this is an automated message. To help Clarity keep track of discussions, we automatically lock closed issues after 14 days. Please look for another open issue or open a new issue with updated details and reference this one as necessary.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants