Info about unsupported APIs

[ivanjeremic]

The docs say "This library doesn't (and it is not going to) polyfill API methods or options that are missing on Chrome but natively provided on Firefox,"

Is there a list of tracked APIs which are not covered?

[rpl]

The docs say "This library doesn't (and it is not going to) polyfill API methods or options that are missing on Chrome but natively provided on Firefox,"

Is there a list of tracked APIs which are not covered?

We do have "browser compatibility" tables as part of the WebExtensions API reference docs on MDN:

• https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs (this page collects all the compatibility tables in one single MDN page, but the same tables are also part of the MDN doc pages documenting the single APIs).

Those compatibility tables are generated from the data available in the following github repos (and so it is where issue related to the browser compatibility details should be filed, and changes submitted as github pull requests).

It would be reasonable to link that MDN doc page in the polyfill README and so I'm marking this issue as needs-docs.

[ivanjeremic]

The docs say "This library doesn't (and it is not going to) polyfill API methods or options that are missing on Chrome but natively provided on Firefox,"
Is there a list of tracked APIs which are not covered?

We do have "browser compatibility" tables as part of the WebExtensions API reference docs on MDN:

• https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_support_for_JavaScript_APIs (this page collects all the compatibility tables in one single MDN page, but the same tables are also part of the MDN doc pages documenting the single APIs).

Those compatibility tables are generated from the data available in the following github repos (and so it is where issue related to the browser compatibility details should be filed, and changes submitted as github pull requests).

It would be reasonable to link that MDN doc page in the polyfill README and so I'm marking this issue as needs-docs.

Thanks from what I see you can't really create useful extensions for Safari if the same extension uses some cool APIs Chrome has. Wonder how long Apple will play this Game...