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

cds-radio-panel checked visual doesn't change when another panel in the same group is selected #42

Closed
2 of 9 tasks
ashleyryan opened this issue Apr 20, 2022 · 4 comments · Fixed by #46
Closed
2 of 9 tasks

Comments

@ashleyryan
Copy link
Contributor

Describe the bug

When rendering multiple radio-panels inside of a cds-radio-group, the other panels don't switch to an unchecked display visually when another panel is checked.

How to reproduce

https://stackblitz.com/edit/clarity-cdn-nlgyj2?file=index.html

Steps to reproduce the behavior:

  1. Notice how clicking "My Radio 1" and then "My Radio 2" unchecks "My Radio 1"
  2. When repeating the same behavior with the radio panel

Expected behavior

A clear and concise description of what you expected to happen.

Versions

Clarity project:

  • Clarity Core

Clarity version:

  • v3.x
  • v4.x
  • v5.x
  • v6.x

Framework:

  • Angular
  • React
  • Vue
  • Other: Vanilla JS

Device:

  • Browser: Chrome
  • Version 100.0.4896.88
@ashleyryan ashleyryan changed the title cds-radio-panel isn't displayed as unselected when another panel in the same group is selected cds-radio-panel checked visual doesn't change when another panel in the same group is selected Apr 20, 2022
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Apr 21, 2022
fixes vmware-clarity#42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Apr 25, 2022
fixes vmware-clarity#42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Apr 25, 2022
fixes vmware-clarity#42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Apr 25, 2022
fixes vmware-clarity#42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Apr 25, 2022
fixes vmware-clarity#42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Apr 25, 2022
fixes vmware-clarity#42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit to ashleyryan/core that referenced this issue Apr 25, 2022
fixes vmware-clarity#42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit that referenced this issue Apr 26, 2022
fixes #42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
ashleyryan pushed a commit that referenced this issue Apr 26, 2022
fixes #42

Signed-off-by: Ashley Ryan <asryan@vmware.com>
@github-actions
Copy link

github-actions bot commented May 2, 2022

🎉 This issue has been resolved in version 5.7.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

github-actions bot commented May 2, 2022

🎉 This issue has been resolved in version 6.0.0-beta.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions
Copy link

github-actions bot commented May 3, 2022

🎉 This issue has been resolved in version 6.0.0 🎉

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 May 18, 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.

1 participant