[FluentSplitButton]: Buttons are not visible like buttons.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- accessibility, frontend
Research direction
Start with the FluentSplitButton component and its demo at the /Nav page, then inspect the attached screenshot to identify which button styling appears missing. Compare the component’s rendered buttons with the project’s button styling and accessibility guidance. Done when both split button parts are visibly recognizable as buttons; the issue does not name a test or source file.
Written by the indexing model from the issue text.
Description
Tags:
#A11yUsable; #TCS-BIC; #FluentUIBlazor_Web; #Win11; #DesktopWeb;CT_FluentUIBlazor_Web_Oct2026;
Test Environment:
Application Name: fluentui-blazor
OS: Windows 11 [Version 25H2 (OS Build 26200.8457)]
Edge: Version 148.0.3967.70 (Official build) (64-bit)
Test URL: https://fluentui-blazor.net/Nav
AT Used: Accessibility Insights for Web.
Repro Steps:
- Launch the URL: https://fluentui-blazor.net/Nav
- Search for FluentSplitButton.
- Verify whether Buttons are visible like buttons or not.
Actual Result:
Buttons are not visible like buttons.
Expected Result:
Buttons should be visible like buttons.
User Impact:
Users may not recognize the elements as buttons, making it difficult to identify that they are interactive and can be activated.
Attachment:
- Dominant language
- C#
- Stars
- 4.9k
- Forks
- 493
- Avg merge
- 21h 50m
- Merged PRs (30d)
- 74
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/fluentui-blazor
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/fluentui-blazor#5546 ·
Maintainers usually reply within 1 day
-
[FluentTabs]: Screen reader does not announce the accessible name and role for the Delete Tab buttonOpen
Difficulty 2/5 Half a day Newbie friendliness 72/100
microsoft/fluentui-blazor#5540 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/fluentui-blazor#5539 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
microsoft/fluentui-blazor#5538 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/fluentui-blazor#5537 ·
Maintainers usually reply within 1 day
All issues in microsoft/fluentui-blazor
Similar issues
-
is:bug is:FQNIssue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nunit/nunit3-vs-adapter#1527 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug effort:S P3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nightscout/nocturne#2840 ·
Maintainers usually reply within 1 day
-
track:release
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
[Bug] [Go] Ack returns nil when the server answers with a non-OK statusPossibly taken @leizhiyuan claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/rocketmq-clients#1465 ·
Maintainers usually reply within 2 days