User:wbamberg

Examples on top

new Request()

Command-line arguments

On Linux and Mac, Chrome passes one argument to the native app, which is the origin of the add-on that started it, in the form: chrome-extension://[extensionID]. This enables the app to identify the add-on.

On Windows, Chrome passes two arguments: the first is the origin of the add-on, and the second is a handle to the Chrome native window that started the app.

allowed_extensions

In Chrome, the allowed_extensions key in the app manifest is called allowed_origins instead.

App manifest location

Chrome expects to find the app manifest in a different place. See Native messaging host location in the Chrome docs. 

FeatureChromeFirefoxEdgeInternet ExplorerOperaSafari
Basic Support1.01.01243.51.0
Multiple backgrounds1.03.612910.51.3
SVG image as background31.09.0129.021.05.1
Values of background-size longhand21.09.0129.021.05.1
Values of background-origin longhand21.022.0129.021.05.1
Values of background-clip longhand21.022.0129.021.05.1
FeatureAndroidChrome for AndroidEdge mobileFirefox for AndroidIE mobileOpera AndroidiOS Safari
Basic Support2.1?(Yes)1.010.05.03.2
Multiple backgrounds2.1?(Yes)1.010.0?3.2
SVG image as background3.0?(Yes)4.010.0(Yes)4.2
Values of background-size longhand3.0?(Yes)18.010.0(Yes)4.0
Values of background-origin longhand3.0?(Yes)22.010.0(No)4.0
Values of background-clip longhand3.0?(Yes)22.010.0(No)4.0

Each article documenting an interface method needs this tag. See RTCPeerConnection.createOffer() for example.

RTCPeerConnection.createOffer()

Old examples on top

List of all pages under "Add-ons"

List of all pages under WebExtensions/API

List of all pages under "CSS"

Document Tags and Contributors

 Last updated by: wbamberg,