I'm a developer on
timyo.com and implement the Gmail chrome extension for our service.
Right now we are using Google API client for javascript. The gapi client itself is the loader script which loads the text of the last version of the gapi client and executes it using eval in the context of the page. We are loading that client in background script and making requests to Google services (Gmail API mostly).
With new manifest the scenario, it will not be possible anymore - it is no dom in ServiceWorke and the Google API client will not work.
There are also 2 standard libs to interact with Gmail:
* open sourced gmailjs
https://github.com/KartikTalwar/gmail.jsIt injects itself into the Gmail page and all legacy iframe and proxying requests to google private API to make triggers to extensions.
Seems that lib will be broken because it will be forbidden to inject the script into the host page.
* the second lib - closed source
https://www.inboxsdk.com/ from StreakCRM. It injects script to host page too and interact with the page almost in the same way as gmailjs. The main issue here - that the lib violates no remote host code.
So generally what we will have in v3
1) no cors requests from content scripts
2) no proxying because it will be impossible to inject the script to host page
3) no Google API client because of it usage of dom
So all mass google extensions based on gmailjs / inboxsdk / Google API client will be impossible to implement with chrome extensions.