Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Half of the chrome privacy API is not available #204
Just noticed that:
Throws the error below:
I'm new to current polyfill library, but having a rough look into the src/browser-polyfill.js seems like there are some privacy APIs that are available in Chrome which are not supported by
Not sure if that is intentional that not all Chrome APIs are supported, but if Chrome API support can be ensured, that will help me a lot making my Chrome Extension also being available in Firefox.
Support for the privacy namespace in the polyfill was introduced in #133, and APIs that weren't supported in Firefox were intentionally left out, because extensions that use those APIs are not cross-browser compatible.
So far, the scope of the polyfill has been to only provide a polyfill to APIs that are implemented by Firefox. I'm not opposed to supporting promises in the full
How would providing a promisified version of the API help you with making the extension available to Firefox, if those APIs are only supported in Chrome?
I see, hmm waiting Chrome switching into using promises don't seem to be something we can expect unfortunately anytime soon :( Same seem to be true for using
My reason is that I'm looking for a polyfill library that will allow me to use both Chrome and Firefox Web Extensions API using a common namespace
Who decides what to support?
Yep, make sense. I'll be happy to update my PR if you say that you want support Chrome API as well.
Plan is to check for the support of each specific Privacy API and load privacy setting switch accordingly in the extension I'm working on. Switching my codebase into using promises and
Updated the PR accordingly, just in case.
Update: Reverted - need some more time to implement that and ensure all tests are passing, will wait for decision before coming back to this issue.
@Rob--W Any idea when new version of the package will be published? Asking that as I'm still using my fork, until builds are available in the NPM package.
Thinking that it would be handy to generate "./dist" on
Thanks in advance.