3 ms·
Chrome is my primary browser, and while I applaud increasing space devoted to content, I wish Chrome had better support for alternate search engines. My primary
by jackfoxy 16y ago
Chrome is my primary browser, and while I applaud increasing space devoted to content, I wish Chrome had better support for alternate search engines. My primary searches are (in order of use) Google, Wikipedia, Amazon. By better support I mean I don't like the way it works in the omni-box. I think the old-fashioned way done in IE8 and FF of having a dedicated search box is much more convenient and easier for most users to configure, but I'm open to other alternatives. I understand IE9 has jumped on the bandwagon and dropped the search box too.
[EDIT] My biggest beef: remembering to substitute underscore for space in Wikipedia search terms.
- tonfa 16y agoAren't keyword search sufficient? Like "w something" to search wikipedia for "something".
- jackfoxy 16y agoOK, I take this one back, but only because wikipedia fixed the problem on their end. If you do the Google Omni-box key-word > tab > search term it formerly worked only with a single search term. If you tried searching for "casey jones", for instance it broke because the omni-box only creates a url, it doesn't use the site's native search engine. So you end up with "%20" between the terms. Apparently wikipedia saw this problem enough times to build in the smarts to redirect to "casey_jones".
- nl 16y agoRegarding the underscore problem, it should be possible to write an extension to fix that using the new OmniBox API. (I don't think plain OpenSearch descriptors can do it themselves though)
- jackfoxy 16y agoExactly my point. Outside of the tiny number of users who have the skill and inclination to write a hack, there are countless more who simply want it to work from the get-go. "Browser" is an unfortunate term for what we do with this kind of software component. Browsing may be the number one thing we use it for, but the second is clearly searching.