-
Notifications
You must be signed in to change notification settings - Fork 1
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
Match rules in webextension limited to only few URI schemes #3
Comments
Other obvious example that does not match: Not working either: All |
Sadly, content scripts can't work with |
Oh come on... Who signed off on all this crap? Why should I want to work with a "secure" browser if it means the browser is unwilling to work with me? Thanks for clarification, but as it stands that means I'll hold of on any update until there's no way around webextensions anymore. |
Update: Firefox Quantum (57) is coming within a week, so it might be a good idea to have the new version submitted to AMO already, so that it can be reviewed and approved in time. |
This is because of limitations in the webextension version, see #3
@ExE-Boss OK, I'm afraid I found an issue with the webextension:
The
"matches": ["<all_urls>"]
inmanifest.json
only works for the URI schemes "http", "https", "file", "ftp" and "app".This fails for example when looking at data URIs.
It's only a minor issue, but as I don't see any real advantage of having a webextension I obviously don't want to sacrifice functionality for it.
The text was updated successfully, but these errors were encountered: