Add support in Chromium for custom input of search engine #523

Closed
craftyguy opened this Issue Dec 7, 2016 · 6 comments

Comments

Projects
None yet
2 participants
@craftyguy

This may be a rather significant addition to Chromium, but given alternative host-your-own metasearch engines (like searx) and other local or regional search engines that people might want to use, this request is to add a 'custom' option in chromium on the Search Engine setting page where the url of any search engine supporting http GET could be input in the form of:

https://example.com?q=%s

Where the %s is input by the user into the custom field and matched/replaced by chromium with the term(s) the user wants to search for (use whatever letter or character(s) you want, this is just an example), and the https://example.com/?q= portion is also input by the user but dependent upon search engine (supporting HTTP GET).

The intention is to provide basic search functionality using a custom-specified search engine url. Any advanced search features (search suggestions, etc) wouldn't need to be supported.

I've seen browsers over the years support this feature (Opera did ~15 years ago when I last used it, if I recall), I can dig around for specific examples if there's some confusion about what this looks like.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 7, 2016

Contributor

Chromium supports this in the desktop UI but they haven't implemented it in the Android UI along with many of the other features.

Contributor

thestinger commented Dec 7, 2016

Chromium supports this in the desktop UI but they haven't implemented it in the Android UI along with many of the other features.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 7, 2016

Contributor

I don't really think I want to maintain something like this out-of-tree. It would have to be done upstream.

Contributor

thestinger commented Dec 7, 2016

I don't really think I want to maintain something like this out-of-tree. It would have to be done upstream.

@craftyguy

This comment has been minimized.

Show comment Hide comment
@craftyguy

craftyguy Dec 7, 2016

Understood, thank you for the quick response.

OMG, also just realized you're the same thestinger who developed termite! THANK YOU!!!

Understood, thank you for the quick response.

OMG, also just realized you're the same thestinger who developed termite! THANK YOU!!!

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Dec 7, 2016

Contributor

I think they would probably happily implement this upstream, the Android UI just needs a lot of work to reach feature parity. Similar to how site settings UI is missing outside of settings, unlike in the desktop UI.

Contributor

thestinger commented Dec 7, 2016

I think they would probably happily implement this upstream, the Android UI just needs a lot of work to reach feature parity. Similar to how site settings UI is missing outside of settings, unlike in the desktop UI.

@thestinger thestinger changed the title from Add suppport in Chromium for custom input of search engine to Add support in Chromium for custom input of search engine Dec 12, 2016

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Mar 18, 2017

Contributor

Supposedly this is implemented for Chrome 57 but I couldn't get it to work on the sites that I tried.

Contributor

thestinger commented Mar 18, 2017

Supposedly this is implemented for Chrome 57 but I couldn't get it to work on the sites that I tried.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jul 9, 2017

Contributor

Visit qwant.com -> do a search -> go to settings -> search engine -> select it in recently visited (note it seems you need to do a search to trigger this).

Contributor

thestinger commented Jul 9, 2017

Visit qwant.com -> do a search -> go to settings -> search engine -> select it in recently visited (note it seems you need to do a search to trigger this).

@thestinger thestinger closed this Jul 9, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment