matatk/landmarks

Disconnect page visibility handling if extension is un-/re-loaded on Chrome-like browsers

matatk opened this issue · 0 comments

The observer itself is disconnected when the extension is unloaded on Chrome-like browsers, so that errors about the extension's context having been disconnected don't appear in the console. The same needs to happen to the mutation stats reporter.

D'oh, this problem wasn't the reporter—realised that it is only triggered by a mutation, and the observer is disconnected—but by the page visibility handling.