AleksanderBodurri bfda774995 fix(devtools): catch invalidated extension error to prevent devtools from spamming console (#55697) ...

When a browser extension is updated it becomes invalidated on currently open pages. If that extension then tries to send a message to those pages through `chrome.runtime.sendMessage(..)` then an error is thrown in the console

For Angular DevTools, this results in spamming the console with "Uncaught Error: Extension context invalidated." errors.

This commit catches that error and removes the event listener that triggers the `chrome.runtime.sendMessage(...)` call.

PR Close #55697

2024-08-27 12:54:44 -07:00

..

demo-no-zone

refactor(devtools): migrate devtools to prettier formatting (#53945)

2024-01-19 19:09:54 +01:00

demo-standalone

refactor(devtools): remove git sha stamping from devtools build (#55694)

2024-05-06 16:02:36 -07:00

ng-devtools

refactor(devtools): Use Chrome DevTools Performance extension API (#55805)

2024-07-31 16:04:52 +00:00

ng-devtools-backend

refactor(devtools): Use Chrome DevTools Performance extension API (#55805)

2024-07-31 16:04:52 +00:00

protocol

fix(devtools): allow DevTools to fail gracefully for unsupported versions of Angular. (#55233)

2024-04-22 11:25:20 -07:00

shared-utils

refactor(devtools): Add hydration informations (#53910)

2024-01-30 20:03:14 +00:00

shell-browser

fix(devtools): catch invalidated extension error to prevent devtools from spamming console (#55697)

2024-08-27 12:54:44 -07:00