Chrome Extension Content Script Re-injection After Upgrade Or Install


Answer :

There's a way to allow a content script heavy extension to continue functioning after an upgrade, and to make it work immediately upon installation.

Install

The install method is to simply iterate through all tabs in all windows, and inject some scripts programmatically into tabs with matching URLs.

Obviously, you have to do it in a background page or event page script declared in manifest.json:

"background": {     "scripts": ["background.js"] },

background.js:

// Add a `manifest` property to the `chrome` object. chrome.manifest = chrome.app.getDetails();  var injectIntoTab = function (tab) {     // You could iterate through the content scripts here     var scripts = chrome.manifest.content_scripts[0].js;     var i = 0, s = scripts.length;     for( ; i < s; i++ ) {         chrome.tabs.executeScript(tab.id, {             file: scripts[i]         });     } }  // Get all windows chrome.windows.getAll({     populate: true }, function (windows) {     var i = 0, w = windows.length, currentWindow;     for( ; i < w; i++ ) {         currentWindow = windows[i];         var j = 0, t = currentWindow.tabs.length, currentTab;         for( ; j < t; j++ ) {             currentTab = currentWindow.tabs[j];             // Skip chrome:// and https:// pages             if( ! currentTab.url.match(/(chrome|https):\/\//gi) ) {                 injectIntoTab(currentTab);             }         }     } });

Upgrade

The upgrade method relies on the fact that the content scripts are left injected after an extension is disabled, uninstalled or upgraded.

When the port connection is made, an onDisconnect handler is added. This waits a second after the disconnect event, then attempts to reconnect. If it fails, another onDisconnect is fired so the process happens again, until a connection is made. It's not perfect, but it works.

The content script:

var port;  // Attempt to reconnect var reconnectToExtension = function () {     // Reset port     port = null;     // Attempt to reconnect after 1 second     setTimeout(connectToExtension, 1000 * 1); };  // Attempt to connect var connectToExtension = function () {      // Make the connection     port = chrome.runtime.connect({name: "my-port"});      // When extension is upgraded or disabled and renabled, the content scripts     // will still be injected, so we have to reconnect them.     // We listen for an onDisconnect event, and then wait for a second before     // trying to connect again. Becuase chrome.runtime.connect fires an onDisconnect     // event if it does not connect, an unsuccessful connection should trigger     // another attempt, 1 second later.     port.onDisconnect.addListener(reconnectToExtension);  };  // Connect for the first time connectToExtension();

The only way to force a content script to be injected without refreshing the page is via programatic injection.

You can get all tabs and inject code into them using the chrome tabs API. For example you can store a manifest version in local storage and every time check if the manifest version is old one (in background page), if so you can get all active tabs and inject your code programmatically, or any other solution that will make you sure that the extension is updated.

Get all tabs using:
chrome.tabs.query

and inject your code into all pages
chrome.tabs.executeScript(tabId, {file: "content_script.js"});


Try this in your background script. Many of the old methods have been deprecated now, so I have refactored the code. For my use I'm only installing single content_script file. If need you can iterate over chrome.runtime.getManifest().content_scripts array to get all .js files.

chrome.runtime.onInstalled.addListener(installScript);  function installScript(details){     // console.log('Installing content script in all tabs.');     let params = {         currentWindow: true     };     chrome.tabs.query(params, function gotTabs(tabs){         let contentjsFile = chrome.runtime.getManifest().content_scripts[0].js[0];         for (let index = 0; index < tabs.length; index++) {             chrome.tabs.executeScript(tabs[index].id, {                 file: contentjsFile             },             result => {                 const lastErr = chrome.runtime.lastError;                 if (lastErr) {                     console.error('tab: ' + tabs[index].id + ' lastError: ' + JSON.stringify(lastErr));                 }             })         }     });     }

Comments

Post a Comment

Popular posts from this blog

Are Regular VACUUM ANALYZE Still Recommended Under 9.1?

Answer : VACUUM is only needed on updated or deleted rows in non-temporary tables. Obviously you're doing lots of INSERTs but it's not obvious from the description that you're also doing lots of UPDATEs or DELETEs. These operations can be tracked with the pg_stat_all_tables view, specifically the n_tup_upd and n_tup_del columns. Also, even more to the point, there is a n_dead_tup column that tells, per table, how much rows need to be vacuumed. (see Monitoring statistics in the doc for functions and views related to statistics gathering). A possible strategy in your case would be to suppress the scheduled VACUUM, keeping an eye on this view and checking on which tables the n_dead_tup is going up significantly. Then apply the aggressive VACUUM to these tables only. This will be a win if there are large tables whose rows never get deleted nor updated and the aggressive VACUUM is really necessary only on smaller tables. But keep running the ANALYZE for the optimiz
Read more

Can Feynman Diagrams Be Used To Represent Any Perturbation Theory?

Answer : Diagram machinery works also for perturbation theory in classical statistical mechanics and classical field theories. Generally, various kinds of diagrams constitute a pictorial way of talking about tensor products and their contractions while hiding the multi-linear algebra from the layman. In the simplest case, vertices (or blobs) represent vectors, matrices, tensors; vertices have ingoing and/or outgoing ports; ingoing ports denote (contravariant) ro indices; outgoing ports denote (covariant) co indices; directed arcs between blobs give a pair of equal indices summed over; different base spaces ⇔ \Leftrightarrow ⇔ different arc types; symmetric tensors ⇔ \Leftrightarrow ⇔ undirected diagrams; no labels are needed for internal lines. In many cases, the directed arcs are decorated (as thin, thick, broken,wavy, curly lines), each decoration indicating the presence of a so-called propagator, a function of its label to use as a weight in the sum, which may beco
Read more