lobiinteractive.blogg.se - Content browser definition

#Content browser definition code

Additionally, however, the manifest does require a value ( default_locale) that is necessary and cannot be specified by the extension author in script code. Use of this API does not require a manifest permission declaration. In this example, the i18n API should be made available to both browser host scripts (background, event, popup, options, etc.) and content scripts. To express the aforementioned conditional situations in which certain APIs are made available due to expressed manifest keys or permissions, the new WebIDL extended attribute " CheckAnyPermissions" is used. ContentScript - Applies to content script context.This applies to background, event, popup, options and custom contexts Window - The primary context for most browser extension APIs.

To express the aforementioned conditional situations in which certain APIs are made available due to context, the following contexts are used: This specification uses WebIDL ] to describe the Browser Extensions API. However, the manifest does require a value ( default_locale) that is necessary and cannot be specified by the extension author in script code. If manifest keys that are not defined in this specification are specified, other browsers MAY elect to ignore those additional keys.īackground page,Event page,Popup page,Options page,Custom pageĤ Use of the browser.i18n object does not require a manifest permission declaration. These requirements are summarized in the table below. If the key or permission are not declared or not granted, the object will not be available for scripting. Some browser extension API require a specific manifest key or specific permission.

Internet-hosted web page context - Messaging APIs can be used to send messages from hosted web site pages such as or to extensions.

Content script context - A limited number of APIs are available to script that extensions use to interact with hosted web site pages.

Custom page - such as "browserext:///m圜ustomPage.html".

Options page - use the "options_page" manifest key.

Popup page - use the "browser_action" or "page_action" manifest key and specify "default_popup".

Event page - use the "background" manifest key and specify "persistent" false.

Background page - use the "background" manifest key and specify "persistent" true.

Browser extension contexts ("Window") - Most extension APIs are available to this context.

The manifest declarations required to create each specific type of page are described below.

Content Security Policy (CSP) for the extension and target web page (for content scripts)Įxecution Context and Manifest Restrictionsīrowser extension pages and their corresponding scripts are executed in one of the following contexts.

contextMenu, tabs, webNavigation, webRequest)

Permissions declared in the manifest (e.g.

background/event, popup, options, content, extension page) However, the specific APIs that are available to an extension from the browser object are dependent upon: In addition to the usual JavaScript Web APIs, additional APIs are available exclusively to extensions via the browser object. GitHub Issues 14 & 17 API Availability Overviewīrowser extensions are authored primarily with JavaScript. Need to resolve ID issue before we can address messaging ('passing data')

accessing user settings such as cookies.

passing data from Internet-hosted web pages to extensions.

UI augmentation for web browsers (host apps).

The goal for these core APIs is to provide functionality that extension authors need for: This will allow extension authors to greatly reduce or eliminate the rework necessary to create extensions that target different browsers.

#Content browser definition code

This Community Group's goal is to make browser extension code much more interoperable across browsers by specifying common extension interfaces and well-defined browser behavior. People interested in this topic are encouraged to join that group.īecause browsers supported different add-on models, extension authors wound up creating divergent codebases and delivering different browser-specific add-ons. With similar objectives but much more active participation, In the meanwhile, a new “WebExtensions Community Group”, The specifications have therefore not been maintained in a while, and are out of date.

The level of participation has dropped below the level at which productive discussion is possible,Īnd activity in this group has stopped as a result. Implementation of the technologies discussed and tentatively specified in this Community Group is ongoingĪnd none of the original contributors have expressed opposition to this work.