fix: Fixing memory leak in a specific DOM change scenario.

microsoft / tabster

Web Application Keyboard Navigation Tools

https://tabster.io

MIT License

116 stars 34 forks source link

fix: Fixing memory leak in a specific DOM change scenario. #366

Closed mshoho closed 4 months ago

mshoho commented 4 months ago

When a node is removed and the attribute of the removed node is changed in the same tick as the removal, MutationObserver gets an event with two mutation records: for both the node removal and the attribute change. That order was causing recreation of untracked Tabster instances.