Closed Bug 1461212 Opened 6 years ago Closed 6 years ago

browserSettings.proxyConfig.set throws error for API example

Categories

(WebExtensions :: General, defect)

60 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1455755

People

(Reporter: 21cmline, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.183 Safari/537.36 Vivaldi/1.96.1147.36

Steps to reproduce:

Developed a trivial web extension implementing the browserSettings.proxyConfig API example. The extension consists of 2 files (manifest.json and background.js), the contents of which are shown below. The extension was loaded using the "Load Temporary Add-on" button on "about:debugging" page.

background.js
----------------
let proxySettings = {
    proxyType: "manual",
    http: "http://proxy.org:8080",
    socksVersion: 4,
    passthrough: ".example.org"
  };
  browser.browserSettings.proxyConfig.set({value: proxySettings});

manifest.json
---------------
{
  "description": "Toggle proxy settings",
  "manifest_version": 2,
  "name": "ProxyToggle",
  "version": "1.0",

  "permissions": ["browserSettings"],

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

  "applications": {
    "gecko": {
      "id": "ProxyToggle@xyz"
      }
    }
}






Actual results:

Proxy settings are not changed. Instead, the following error is thrown:
    fun is not a function
    Error: An unexpected error occurred


Expected results:

Proxy settings should have changed accordingly. Works as expected with 59.0.3.
User Agent in which bug occurred is:

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
API has changed and documentation updated.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.