Right now, we request permission to act on tabs, which causes Chrome to warn the user on install that the extension will have access to "your tabs and browsing activity" or some such.
This is unsettling, and unneeded - we only use the tabs interface to enable the page action icon when a Pardus page is loaded. This perhaps should be done in an content script.
Right now, we request permission to act on tabs, which causes Chrome to warn the user on install that the extension will have access to "your tabs and browsing activity" or some such.
This is unsettling, and unneeded - we only use the tabs interface to enable the page action icon when a Pardus page is loaded. This perhaps should be done in an content script.