Firefox WebExtention API: TypeError: browser.browserAction is undefined [duplicate]
Asked Answered
P

1

8

While migrating my old Firefox add-on to WebExtension API, failed to understand while I am getting this error:

TypeError: browser.browserAction is undefined

Here is the manifest.json:

{

  "manifest_version": 2,
  "name": "My Login",
  "version": "3.0",

  "description": "Login to my page",
  "homepage_url": "https://localhost",
  "icons": {
    "48": "icons/button-1.png"
  },

  "permissions": [
    "activeTab", "storage"
  ],

  "browser_action": {
    "default_icon": "icons/button-1.png",
    "default_title": "Login"
  },


  "content_scripts": [
    {
      "matches": ["<all_urls>"],
      "js": ["index.js"]
    }
  ],

  "options_ui": {
    "page": "options.html"
  }
    }

Here is the index.js:

function handleClick() {


    var loginUserName, loginPassword;

    var URL = window.content.location.href;

    var doc = window.content.document;


}

browser.browserAction.onClicked.addListener(handleClick);

So I am getting TypeError: browser.browserAction is undefined in the browser console when I go to about:debugging and load my add-on as a temporary addon.

Options.html, options.js and button-1.png do exist - I just don't place them here.

Observed in Firefox 55.0.3 (32-bit). Any idea why this error happens?

Thanks, Racoon

Playwright answered 6/9, 2017 at 17:37 Comment(1)
As this question is unfortunately marked as a duplicate I can't add another answer to this. I had a similar problem due to the fact that I simply forgot to define a browser_action in my manifest.json. See here: https://mcmap.net/q/766062/-typeerror-api-is-undefined-in-content-script-or-why-can-39-t-i-do-this-in-a-content-scriptOzoniferous
S
8

browser.browserAction should be called in a background script and not in a content script like you're doing. So assuming this code is in background.js:

function handleClick() {
    console.log("do something.");
    // If you want to something with the content, you will need a content script and messaging
}

browser.browserAction.onClicked.addListener(handleClick);

You add the background_scripts key in manifest.json:

{

  "manifest_version": 2,
  "name": "My Login",
  "version": "3.0",

  "description": "Login to my page",
  "homepage_url": "https://localhost",
  "icons": {
    "48": "icons/button-1.png"
  },
  "background": {
    "scripts": ["background.js"]
  }
}
Stodgy answered 6/9, 2017 at 18:2 Comment(3)
Thanks, it seems to work, but I was going to use a content script to change the value of some web elements. Something like doc.getElementById("loginUserName").value = loginUserName; Can I do this with a background script, or I need to use a combination of a background and content scripts?Playwright
It looks like I do need a content script in addition to the background script: #46099197Playwright
Yes, you will need both a background script (for most WebExtension APIs) and a content script to alter page contents.Stodgy

© 2022 - 2024 — McMap. All rights reserved.