Will something bad happen if we request these permissions again as optional permissions? This makes them much less scary since you can safely install extensions without granting these optional permissions.įor our extension, you can choose to grant these optional permissions on our extension’s options page. Optional permissions must be specifically granted by users after installation. We’re going to try adding them as optional permissions instead of requiring them right away. So how do we get these permissions after Google had us remove them?

The Pushbullet extension uses this permission to be able to push images and files from websites that do not permit Cross-Origin Resource Sharing (CORS) as documented here by Google for Chrome extensions. The and permissions grant extensions access to data on all webpages. Pushbullet uses this permission to avoid opening new tabs for websites that are already open when mirrored notifications are clicked. The tabs permission lets extensions see what tabs are open.

In our case, however, they are required to enable some valuable functionality: The permissions we removed while trying to get our extension approved were tabs, and These permissions grant access to private information and can be misused. Here’s our challenge: make our extension work for you as well as it did before all while continuing to require less permissions. It has become clear over the past few weeks, however, that those permissions enabled our extension to work better than it does now without them. To meet Google’s requirements and stay in the Chrome Web Store we needed to remove a few permissions from our extension. Three weeks ago Google was close to removing our Chrome extension from the Chrome Web Store.

Chrome pushbullet