i'm developing chrome extension uses proxy api. in manifest, declare permission in example:
{ "manifest_version": 2, "version": "0.1", "name": "my extension", "content_scripts": [{ "matches": ["localhost"], "js": ["content.js"], "run_at": "document_start" }], "permissions": [ "proxy" ] } this worked in mid-april, loading (in browser, , in coworker's) chrome proxy api never available (even when switching extension/content.js context in chrome dev console) - chrome.proxy undefined.
the docs don't mention it, has chrome.proxy api been deprecated?
based what's new in extensions, starting google chrome 13, chrome.proxy api relies on chromesetting prototype of type api getting , setting proxy configuration.
in chrome setting documentation, stated that:
chromesetting prototype provides common set of functions (
get(),set(), ,clear()) event publisher (onchange) settings of chrome browser.
chrome distinguishes between 3 different scopes of browser settings , manages setting on different layers may influence effective settings, in increasing order of precedence.
- system settings provided operating system
- command-line parameters
- settings provided extensions
- policies
as list implies, policies might overrule changes specify extension. can use
get()function determine whether extension capable of providing setting or whether setting overridden.
please try go through documentations more details regarding changes in proxy configuration.
