I'm trying to understand the purpose of the observeOwnChanges option.
Looking at the Mutation Summary source, it seems that if observeOwnChanges
is set to false, then anytime the Mutation Observer API executes the
callback, it disconnects the observer after pulling the mutations, creates
summaries from them, returns those summaries inside the passed callback,
and then reconnects the observer. Why would it be necessary to do this? If
observeOwnChanges is set to false, then won't the mutation summary library
fail to report any mutations that occurred on the page while it was
creating the summaries?