CODEWITHSUNDEEP
error-handlinggoogle-chrome-extension
sunki
sunki

Reputation: 673

Background js doesn't work on error pages

Is there any way to load background js even on error pages (such as net::ERR_NETWORK_CHANGED)? I need to keep persistence connection with WS server from the extension, but error pages don't load background js. So I lose the connection and possibility to restart it (due this is automated tool without access to browser ui).

The only solution I found is to use proxy server to customize error pages and load background js inside of them.

Upvotes: 0

Views: 602

Answers (1)

Rob W
Rob W

Reputation: 349032

The assertion "Background js doesn't work on error pages" does not make any sense, because there's only one background page per extension two if you use split incognito mode.

So I assume that you want to detect a network connectivity loss in order to restore the web socket. Chrome offers two reliable global events for this: online and offline.

I have published the source code of Real-time desktop notifications for Stack Exchange inbox, which also accounts for network connectivity loss/regain. The relevant Web Socket part of the Chrome extension is found in stackexchange-notifications/Chrome/using-websocket.js on Github.

Upvotes: 2

Related Questions