Google-api-javascript-client: Compatibility with Chrome's Manifest V3 extension platform

[dotproto]

Chrome is in the process of transitioning to extension developers to a new extension platform called Manifest Version 3 (MV3). ThisNew platform introduces a number of changes to improve the security and privacy of extension users. One of the major changes coming to the platform is that extensions will no longer be allowed to run code retrieved from remote servers. In other words, extensions won't be able to fetch and https://apis.google.com/js/api.js as described in the Getting Started guide.

On the Chrome extension team, we have been advising developers to package third-party libraries with their extensions in order to work around this limitation. I'm not personally familiar with the JS GAPI library, so I'd like to ask whether this guidance it's appropriate for this library or whether we need to explore alternative approaches.

[sergentj]

Hi, no, it's not possible for third-party developers to bundle GAPI with
their applications.

>

[kospl]

This is known bug, circa 2012:
https://github.com/google/google-api-javascript-client/issues/586
https://github.com/google/google-api-javascript-client/issues/312
https://github.com/google/google-api-javascript-client/issues/261
https://github.com/google/google-api-javascript-client/issues/64

[Arthur404]

https://www.google.com/recaptcha/api.js - here are the comments that this code DO NOT COPY AND PASTE.
It's not possible to add a recaptcha to the extension Manifest V3 if don't allowed to add third party code

[thdoan]

I hope that GAPI and Extensions teams can agree on a "whitelist" of vetted libraries that can be remotely hosted if a bundling solution does not come to fruition.