1502726 - window.browser and window.chrome are undefined in content script

Status: RESOLVED DUPLICATE of bug 1208775

(WebExtensions :: General, defect)

Description

[NN]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0

Steps to reproduce:

In content script of any extension the objects chrome and browser are defined.
But window.chrome and window.browser are undefined.



Expected results:

window.chrome should be defined and equal to chrome, window.browser should be equal to browser.

Comment 1

[Tooru Fujisawa [:arai]]

content script doesn't have them by design
things available there is listed here:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts#WebExtension_APIs

if you want to access other API, you need to talk to background script by message.

Comment 2

[NN]

Here is console output from content script:

chrome
Object { menus: Getter & Setter, manifest: Getter & Setter, i18n: Getter & Setter, test: Getter & Setter, storage: {…}, runtime: {…}, extension: {…} }

browser
Object { menus: Getter & Setter, manifest: Getter & Setter, i18n: Getter & Setter, test: Getter & Setter, storage: {…}, runtime: {…}, extension: {…} }

window.chrome
undefined

window.browser
undefined

In JavaScript all objects are part of global object called window.
There is no reason to make these two objects special.

Comment 3

[Tooru Fujisawa [:arai]]

oops, sorry I completely misunderstood.