-
Notifications
You must be signed in to change notification settings - Fork 16
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
Make it available for Firefox Android #20
Comments
I am only using the new Firefox for Android (Beta/Nightly), which only has a limited sub-set of extension so I can't test this. |
@missmatsuko you are right, this should cover 99% of people's use cases. firefox will always verify the domain you are entering and does not allow you to add it when that verification fails. i think they could have left it with a warning and it would have been alright, but for some reason they didn't and left us in this weird situation. you can easily simulate this by trying to add a search engine of some made up domain, which doesn't exist. this addon would still work fine in this scenario as it doesn't perform any checks. so, that would be one reason why it would be nice to have it on mobile as well. |
@fschrofner did firefox say why it failed validation? Is it just https maybe? I don't know why it'd be different for an extension. |
It does not explicitly mention why the error occurs, it just shows a generic error message. But based on the behavior I believe that it's related to the basic authentication. It works fine for searx instances which do not require authentication. I don't know the implementation details so I'm not sure how it is handled internally, but this addon does not enforce any checks when adding the search engine and therefore does not prevent you from adding it even when it might be broken. This is arguably better than blocking it for users who know what they are doing. |
Not sure if it's easily doable, but right now the add-on is not available on Android.
Would be nice if it's just a flag to set, so that we can use the same search engines on mobile.
The text was updated successfully, but these errors were encountered: