Closed tunetheweb closed 1 year ago
Updated implementation to feed through the message after all. Note, this supersedes #143 as it's a better solution that also switched to using console.log
rather than console.error
and so stops surfacing these "expected" errors to the chrome://extensions screen.
We occasionally see reviews, or complaints on Twitter like this:
I noticed on our Corp machines when looking at some sites (e.g. www.youtube.com) we get a
This page cannot be scripted due to an ExtensionsSettings policy.
error in the service worker console, so suspect this is the cause of a lot of these errors.~I think a quick fix here, rather than surfacing the exact error and feeding it through from the service worker to the popup page~ Actually I changed my mind and did it the full way after all.
Fixes https://github.com/GoogleChrome/web-vitals-extension/issues/118 Fixes https://github.com/GoogleChrome/web-vitals-extension/issues/54 Fixes https://github.com/GoogleChrome/web-vitals-extension/issues/56 As handles exceptions better and so switched from
console.error
toconsole.log
as no need to surface them in thechrome://extensions
page anymore.