microsoft / microsoft/fluentui

[Bug]: fluent-radio-group component not working as expected

Open
#31,131 5 comments 0 reactions 1 assignee View on GitHub

@chrisdholt is already working on this.

Since Apr 22, 2024.

Resolution: Soft Close web-components
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Library

Web Components (@fluentui/web-components)

System Info
System:
    OS: Windows 10 10.0.22631
    CPU: 12th Gen Intel(R) Core(TM) I5-12400 2.5GHz
    Memory: 2.41 GB / 31.8 GB
  Browsers:
    Edge: Chromium (124.0.2478.51)
    Internet Explorer: 11.0.22621.1
Are you reporting Accessibility issue?

None

Reproduction

see screenshot

Bug Description

Actual Behavior

bug fluent-radio-group

Always select the last one when clicking for the first time.

Code:

<!DOCTYPE html>
<html lang="en">
<head>
    <script type="module" src="https://unpkg.com/@fluentui/web-components"></script>
    <title>fluent-radio-group</title>
</head>
<fluent-radio-group orientation="vertical" name="radio-story">
    <fluent-radio name="Radio1" style="padding: 20px 0 20px 0;">Radio 1</fluent-radio>
    <fluent-radio name="Radio2" style="padding: 20px 0 20px 0;">Radio 2</fluent-radio>
    <fluent-radio name="Radio3" style="padding: 20px 0 20px 0;">Radio 3</fluent-radio>
    <fluent-radio name="Radio4" style="padding: 20px 0 20px 0;">Radio 4</fluent-radio>
</fluent-radio-group>
</html>

If the version is changed to ”https://unpkg.com/@fluentui/web-components@2.0.0“ There won't be any secondary issues.

Expected Behavior

Select the option you clicked on for the first time.

Logs
no logs
Requested priority

Normal

Products/sites affected

No

Are you willing to submit a PR to fix?

no

Validations
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • The provided reproduction is a minimal reproducible example of the bug.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.