-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension doesn't work in "tiles/Top page". #28
Comments
Modern WebExtensions API doesn't provide access to browser's restricted pages (about:…, chrome://…) and to browser itself. :( Only possible to enable on some restricted http/https pages like addons.mozilla.org, in about:config: |
I've updated list of WE-version limitations: |
That's a shame, but not your fault. Thank you for your prompt response, I have incorporated your suggestions. |
@Infocatcher I always leave those 2 settings as defaults, because I do not currently fully understand all the security implications of changing them. The biggest risk seems to be an installed rogue extension to which the user has given the "Access all websites" permission. It could then modify those restricted pages and trick a user into downloading more malware. But, honestly, if they already have rogue code running and it has access to all non-restricted web pages, their browser is completely compromised already. Do you happen to understand all the risks involved? Not that I'm going to change those settings, but it would be good to learn the details if you know them. |
With online banking & Co there is too many things to stole even without tricking restricted pages like AMO. I think, the most important part about secure extensions – is something like manual review, and this part is now skipped in favor of some automated tests during uploading to AMO and signing. |
It looks like no one has requested such API on Bugzilla yet, right...? |
It also doesn't work when trying to open a bookmark. I ask because I just switched from Waterfox Classic and I could do both of those things with that browser.
The text was updated successfully, but these errors were encountered: