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
FocusZone: removing keydown listener correctly. #11689
Conversation
The related PR also had a fix to |
Component Perf AnalysisNo significant results to display. All results
|
Asset size changes
Over Tolerance (1024 B) Over Baseline Below Baseline New Removed 1 kB = 1000 B Baseline commit: f82bc1ef3402bda4ff6d49a2d44579bd27f36a49 (build) |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for cherry-picking this fix @dzearing! This will fix a % of leaks we see when profiling the list across OneDrive / SharePoint cc: @ThomasMichon @patmill
Nevermind, @JasonGore you're right it is nested inside the |
@JasonGore For symmetry, I moved the same dispose logic into the !innerzone block in unmount. |
🎉 Handy links: |
🎉 Handy links: |
In nested FocusZones, a global keydown listener is added but not removed. This should address this and only add it on the first outer zone and remove it on the last outer zone.
Microsoft Reviewers: Open in CodeFlow