You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you run the command vite and you run it, you can't see the blue checkmark on the selected rows in the DetailedList Component. See repoduction where I created a default vite project and added the detailedList example from the documentation. When you select an row, you don't see the blue checkmark showing that the row is selected.
Expected Behavior
When you run vite you can see the checkmarks when you select an row.
Logs
No response
Requested priority
Normal
Products/sites affected
No response
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.
The text was updated successfully, but these errors were encountered:
If you remove <StrictMode> in main.tsx the issue disappears. Obviously this is not an actual solution, but a workaround 🙂
This issue will need more debugging to find the root cause but in the past I've seen it related to class component lifecycle methods. For example, an event listener is wired up in a constructor and torn down in componentWillUnmount so it can never be reconnected.
Library
React / v8 (@fluentui/react)
System Info
Are you reporting an Accessibility issue?
None
Reproduction
https://codesandbox.io/p/sandbox/vite-fluent-ui-demo-8zglrm
Bug Description
Actual Behavior
When you run the command
vite
and you run it, you can't see the blue checkmark on the selected rows in the DetailedList Component. See repoduction where I created a default vite project and added the detailedList example from the documentation. When you select an row, you don't see the blue checkmark showing that the row is selected.Expected Behavior
When you run
vite
you can see the checkmarks when you select an row.Logs
No response
Requested priority
Normal
Products/sites affected
No response
Are you willing to submit a PR to fix?
no
Validations
The text was updated successfully, but these errors were encountered: