Skip to content
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

Chromium-based browsers (Android) don't detect searx #1666

Open
samantohermes opened this issue Aug 2, 2019 · 5 comments

Comments

@samantohermes
Copy link

commented Aug 2, 2019

No description provided.

@dalf

This comment has been minimized.

Copy link
Collaborator

commented Aug 3, 2019

It requires more information :

  • Chromium-based browsers: which one ? is Chrome or another browser ?
  • what do you mean by "detect" ?
@samantohermes

This comment has been minimized.

Copy link
Author

commented Aug 3, 2019

  1. I tested in Chrome and Bromite
  2. I meant by "detect" being able to set as the default engine: https://coinsh.red/u/Screenshot_20190803-171609_Bromite.png
@samantohermes

This comment has been minimized.

Copy link
Author

commented Aug 3, 2019

Should appear in the "recently visited"

@unixfox

This comment has been minimized.

Copy link
Contributor

commented Aug 5, 2019

Did you do a search on the Searx instance? According to this comment on the chromium bug tracker you need to do a search on the search engine before being able to add it as a default search engine.

@samantohermes

This comment has been minimized.

Copy link
Author

commented Aug 5, 2019

Yes, I did a search in the searx instance.

@samantohermes samantohermes changed the title Chromium-based browsers (Android) don't detect Searx Chromium-based browsers (Android) don't detect searx Aug 5, 2019

@dalf dalf added the bug label Aug 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.