![]() No callback supported by the Promise-based APIs on Chrome This section aims to keep track of the most common issues that an extension may have. This library tries to minimize the amount of "special handling" that a cross-browser extension has to do to be able to run on the supported browsers from a single codebase, but there are still cases when polyfillling the missing or incompatible behaviors or features is not possible or out of the scope of this polyfill. Only contains types for chrome extensions though! Manually maintained types based on MDN's documentation. Formerly known as webextension-polyfill-ts. There are multiple projects that add TypeScript support to your web-extension project: and JS-Doc are automatically generated from the mozilla schema files, so it is always up-to-date with the latest APIs. ![]() The npm package is named after this repo: webextension-polyfill.įor the extension that already include a package.json file, the last released version of this library can be quickly installed using:Ĭonst CopyWebpackPlugin = require ( 'copy-webpack-plugin' ) module. InstallationĪ new version of the library is built from this repository and released as an npm package. On Firefox, this library is actually acting as a NO-OP: it detects that the browser API object is already definedĪnd it does not create any custom wrappers.įirefox is still included in the automated tests, to ensure that no wrappers are being created when running on Firefox,Īnd for comparison with the behaviors implemented by the library on Chrome. The polyfill is being tested explicitly (with automated tests that run on every pull request) on officially supportedīrowsers (that are currently the last stable versions of Chrome and Firefox). Unofficially Supported as a Chrome-compatible target (but not explicitly tested in automation) Officially Supported as a NO-OP (with automated tests for comparison with the behaviors on Chrome) Officially Supported (with automated tests) Known Limitations and Incompatibilities. ![]() Missing feature on its own or enable/disable some of the features accordingly). ![]() On Firefox, and so the extension has to do its own "runtime feature detection" in those cases (and then eventually polyfill the This library doesn't (and it is not going to) polyfill API methods or options that are missing on Chrome but natively provided W3 Browser Extensions group to run on Google Chrome with minimal or no changes. This library allows extensions that use the Promise-based WebExtension/BrowserExt API being standardized by the ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |