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
The modal should not be retained as a detached element. Even though this does not cause a bad memory leak (memory does not continue bloating) it's still bad because sensitive information can still be leaked from the modal.
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:
This is actually React working as intended and there's nothing we can actually do about it.
Also this is not what we've considered a real leak since the detached HTML element count does not actually increase. React will keep two separate trees in memory for optimization purposes and there is an open issue on their end stating that detached elements in alternate trees won't be fixed any time soon facebook/react#16087.
Library
React / v8 (@fluentui/react)
System Info
Are you reporting Accessibility issue?
No response
Reproduction
https://codesandbox.io/s/z388du?file=/src/index.tsx
Bug Description
Actual Behavior
In edge:
Expected Behavior
The modal should not be retained as a detached element. Even though this does not cause a bad memory leak (memory does not continue bloating) it's still bad because sensitive information can still be leaked from the modal.
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: