Search engine woes

  • How do I configure search-engines?

    • I added a custom search engine, but made a spelling error in the name. How do I correct that?
    • How do I change the default order. Somehow Google is selected every time I startup Opera. I have to change it manually every time to something more privacy safe, DuckDuckGo or Disconnect, and working. Google is totally useless on Tor networks. It forces a Captcha: it doesn't like users it can't track. That is exactly the reason I don't like Google. Opera was always the best friend of any internet user. Now it seems to be Google's best friend. Disappointing and short term sight. But maybe I oversee a feature. How do I set any custom search engine as default. Or should I use Firefox for this.
    • Can't add search engines, that use new fashionable JavaScript driven forms, that actually don't use a HTML form element. Although the url still uses GET parameters, I can edit it manually, because I can't edit it manually. And I can't add it with a longpress, because it isn't a form specwise: it has no form element in HTML.
  • @janghou I agree I'd like to see this sorted out as well. It's not really a technical issue, more a good UXG solution that needs to be produced. Thanks for the info on non-form search engines, haven't really thought about that earlier. Do you have any good examples of that?

  • speaking of duckduckgo, is there any reason that opera 28 on the desktop includes duckduckgo as an included search engine, but opera on android doesn't? Could that be added in the future?

  • I don't think there's a deliberate decision to exclude it. It comes down to limited UI space I'd say, the list is already quite long. It's easy enough to add a new search engine by long pressing the search field if you want to... we just need to sort out the UXG problem discussed above to make it even better.

  • @emoller, thx, it annoys me for a couple of years and now you ask me I, only two examples come up directly

    but myriad more on JS driven sites.

    Also for consideration, support for Sitelinks Search Box, search defined in JSON-LD or other microdata.

    https://developers.google.com/structured-data/slsb-overview
    <script type="application/ld+json">
    {
    "@context": "http://schema.org",
    "@type": "WebSite",
    "url": "https://www.example-petstore.com/",
    "potentialAction": {
    "@type": "SearchAction",
    "target": "https://query.example-petstore.com/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
    }
    }
    </script>
    See that a lot nowadays in Wordpress driven sites, even a physical search-box is not necessary here.

    I would prefer an option to remove unwanted default engines, it sucks to have space eaten by services from multinationals I don't like / want to do business with. On my tablet the first engine I can add, is always hidden, so I have to scroll to it.

    Opera always complained about MS behaviour of bundling and pushing certain services or products. Opera does the same now, and it can only do it because it's too small to be able to misuse market-power. I don mind default settings, as long as it's a setting. Search engine should be a setting. And I wonder where to disable suggestions. I really think it´s a privacy concern. People are not aware all they type is transferred to Google right away, without any consent (before they press search)

Log in to reply
 

Looks like your connection to Opera forums was lost, please wait while we try to reconnect.