Open jeanjacquescollective opened 11 months ago
can you confirm that you've selected Always Allow On hoppscotch.io
on the extension settings. We've upgraded to Manifest V3 in the latest release, which gives users more control over the extension permissions.
Here is how to enable it if you need it,
Always Allow On hoppscotch.io
Always Allow On hoppscotch.io
fixes this issue.
But there is another problem: "Could not send request"
Everything works only if I enable Access your data for all websites
.
But in this case, the active origins list makes no sense.
I had the same troubles of setting the extension up.
There should be some hint regarding the 2 necessary options mentioned by you two above:
Have same issue here. Only after enabling "Access your data for all websites" request to e.g. "https://www.google.de" can be made
Using Firefox 122.0.1 (64-Bit) Hoppscotch Plugin Version 0.31
I experienced this same issue and kept tinkering around in my user.js to see if it was a profile issue, but it was apparently a manifest v3 issue?(not really an issue).
This Section mentions that the host_permissions are optional and that extensions do not prompt the user to provide these permissions as of now.
Most browsers treat host_permission as optional. If you request permissions using this key, users may get prompted to grant those permissions during installation. As of June 2023, Safari, Firefox, and some Chromium-based browsers don't prompt the user during installation.
This is true even today February 2024
This issue can be solved by prompting the user to provide access to ://hoppscotch.io/ by using
browser.permissions.contains({
origins: ["*://hoppscotch.io/*"],
})
This shall get a Promise<boolean>
The documentation for this can be found here
This issue is Firefox specific and does not seem to affect Chromium.
Prompting the user to provide the permission would be the most friendly approach to solve this imo.
The popup can give a warning and reference which shows how to provide the necessary permissions.
Newest version of the plugin (Version 0.28) doesn't work on both Firefox Developers Edition 121.0b9 (64-bit) and Firefox.
Fix: Rolled back to version 0.25 and the issue was gone.