This repository was archived by the owner on Sep 5, 2022. It is now read-only.
This repository was archived by the owner on Sep 5, 2022. It is now read-only.
[Watcher] Options for MutationObserver when dealing with a lot of DOM mutations #17
Description
If very expensive DOM mutations are being made, watching all of those can be a performance hit. The Watcher should have an option in its init() method to just go over the entire <body>, init any components it finds, and not start a MutationObserver.
There could also be an attribute like ob-watcher-ignore or a predicate function that can short-circuit the mutations check and allow the user to optimize the Watcher by making it avoid checking large DOM trees.