Home/ Questions/Q 8076091
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T15:11:27+00:00

I am using the following code to access the background page function in google

  • 0

I am using the following code to access the background page function in google chrome

popup.html

function sendRequest(ea,eb)
{
console.log("Inside");
chrome.extension.sendRequest({ea:ea,eb:eb},
        function(response)
        {
            alert(response.farewell);

        });    
}

background.html

<html>
<body>
<script>
chrome.extension.onRequest.addListener(
  function(request, sender, sendResponse) {
sendResponse({farewell: "goodbye"});
  })
</html>
</body>
</script>

manifest.json

{
  "name": "My First Extension",
  "version": "1.0",
  "manifest_version": 2,
  "background": {
    "page": "background.html"
  },
"content_scripts": [
    {
      "matches": ["http://*/"],

      "js": ["popup.js"]
    }
  ],



  "description": "The first extension that I made.",
  "browser_action": {
    "default_icon": "icon.png",
    "default_popup": "mine.html"
  },
  "permissions": [
    "tabs","http://*/","background"

  ],
   "web_accessible_resources": ["loading.html","bu.png"] 


 }

However it does not print the alert. Can anyone tell me what i am doing wrong here?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your HTML for background.html is extremely malformed and should be fixed;

    <html>
<body>
<script>
  chrome.extension.onRequest.addListener(
    function(request, sender, sendResponse) {
  sendResponse({farewell: "goodbye"});
    })
</script>
</body>
</html>

    Tags should be closed in the reverse order of them being open to maintain a correct hierarchy. Since you had not done so, the <script> element was malformed and contained invalid syntax </html></body> so would not be executed correctly.

    Since you’re using version 2 of the manifest you may want to consider abstracting the contents of this script element (ignoring all HTML) to its own file (e.g. background.js) and change your manifest to the following;

    {
  "name": "My First Extension",
  "version": "1.0",
  "manifest_version": 2,
  "minimum_chrome_version": "18",
  "background": {
    "scripts": ["background.js"]
  },
"content_scripts": [
    {
      "matches": ["http://*/"],

      "js": ["popup.js"]
    }
  ],



  "description": "The first extension that I made.",
  "browser_action": {
    "default_icon": "icon.png",
    "default_popup": "mine.html"
  },
  "permissions": [
    "tabs","http://*/","background"

  ],
   "web_accessible_resources": ["loading.html","bu.png"] 


 }

    Notice that the background property now contains an array of strings representing JavaScript files to be loaded (in the order specified) in to a dynamically generated background page.

    I’ve also set the minimum_chrome_version property to 18 as manifest version 2 should only be used when targeting this version of Chrome and above.

    Developers should now only really need to use background pages instead of scripts when they need to support older versions of Chrome.

    Edit

    It just clicked that you’re attempting to execute embedded JavaScript within your background page. Manifest version 2 introduces Content Security Policies which prohibit the execution of inline (e.g. onclick="showDialog();" and href="javascript:void(0);") and embedded JavaScript. This is why your background.html won’t work and why background.js will. You will also want to ensure your popup.html doesn’t contain any embedded JavaScript. The best workaround (and generally best practice anyway) is to abstract all JavaScript into its own file (e.g. popup.js) which is referenced by the HTML file. For example;

    <script src="/popup.js"></script>
    • 0