Hacker News new | ask | show | jobs
by HeavyFeather 1170 days ago
I don’t see any changes on the repo. The permissions in your case should just be activeTab and storage. That’s it.

You can run the extension via chrome.browserAction.onClick and it will receive the URL. You also don’t need the tabs permission just to create a tab.
1 comments
codingpanic 1170 days ago
The issue is that if you do not set permissions in the manifest, clicking allow in the safari UI would only return a blank URI, "". The original extension in this case would also just return an error.

I've modified the manifest so that it is asking Safari for wider permissions, so that when the permission is granted by the user, the proper URL is returned.

link
HeavyFeather 1170 days ago
I think that’s a Safari bug with activeTab, you just have to click twice.

Regardless, with activeTab you can just inject script into the page itself through which you can open a regular popup.

    chrome.scripting.executeScript({
      func: () => window.open(' archive.ph' + location.href)
    })
Currently the extension will suggest that it needs access to every page the user visits, occasionally opening a popup automatically if I remember correctly.

For something that’s a glorified bookmarklet, that’s a lot to ask.

link