Question

48

Google Chrome Extension - Script Injections

rated 0 times [ 55] [ 7] / answers: 1 / hits: 44528 / 12 Years ago, thu, may 10, 2012, 12:00:00

I'm trying to get my Chrome Extension to inject some javascript with content_scripts, using this previous answer as a reference.

manifest.json

name: My Chrome Extension,

version: 1.0,

manifest_version: 2,

content_scripts: [{

    matches: [http://pagetoinject/script/into/*],

    js: [contentscript.js]

}]

contenscript.js:

var s = document.createElement('script');

s.src = chrome.extension.getURL(script.js);

(document.head||document.documentElement).appendChild(s);

s.parentNode.removeChild(s);

( also tried this method with no success. )

var s = document.createElement('script');

s.src = chrome.extension.getURL(script.js);

s.onload = function() {

    this.parentNode.removeChild(this);

};

(document.head||document.documentElement).appendChild(s);

I keep getting this javascript error. Here's a screenshot.

enter
GET chrome-extension://invalid/ (anonymous function)

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

lara

Add To Favorites

Follow

Total Points: 462

Total Questions: 100

Total Answers: 102

Location: Jersey

Member since Mon, Jun 14, 2021

3 Years ago

lara questions

1 How to watch for multiple values in Vue 3 script setup?

Thu, May 19, 22, 00:00, 2 Years ago

1 chrome.runtime.OnMessage.addListener returns duplicate messages

Tue, Jul 27, 21, 00:00, 3 Years ago

1 Using try catch in watch of Vue.js

Thu, Apr 1, 21, 00:00, 3 Years ago

1 NodeJS 12 SyntaxError: Unexpected token 'export'

Mon, Jul 27, 20, 00:00, 4 Years ago

1 In Blazor Server-Side how can I detect if the user tries to navigate off of the current page

Tue, Mar 17, 20, 00:00, 4 Years ago

View All

answered 12 Years ago havenbilliec · Accepted Answer

In your manifest file, manifest_version: 2 is specified. This automatically activates a stricter mode, in which all extension's files are not available to web pages by default.

Your original code would never work, because the <script> element is immediately removed after injection (the script file does not have a chance to load).

As a result of 1., the following error shows up in the console:

Failed to load resource                             chrome-extension://invalid/

To fix the problem, add script.js to the whitelist, web_accessible_resources in your manifest file:

{

  name: Chrome Extension,

  version: 1.0,

  manifest_version: 2,

  content_scripts: [{

      matches: [http://pagetoinject/script/into/*],

      js: [contentscript.js]

  }],

  web_accessible_resources: [script.js]

}