An update for anyone reading this. First, I wanna thank @andrew84 for mentioning my topic along with others in a comment on an Opera blog post. After that, I was able to find useful information about the issues I pointed out here.
@burnout426 said in I'm missing the "Create search engine" entry:
However, when you visit supported sites like Youtube that tell browsers how to search the site, you will see that a search engine for it is now automatically added to the
opera://settings/searchEnginespage where all you have to do is click "Activate" for it, and then edit its keyword if you want.
@burnout426 said in I'm missing the "Create search engine" entry:
The whole autodetect + activate thing just comes from Chromium that Opera turned on. Opera's context menu search engine enumeration just isn't set up to skip inactive engines yet. I consider that a bug.
So, as burnout426 said there, Chromium added the feature "Tab to search", basically, the website provides the URL used in its searches, and the browser might automatically add it as a search engine. For these websites, DevTools shows the OpenSearch document they expose.
Opera Forums:

Playwright:

The Chromium article also explains why visiting homepage (commonly origin without a path) adds the search engine:
For 1 and 2 Chromium only adds sites that the user navigated to without a path. For example
http://mysite.com, but nothttp://mysite.com/foo.
That being said, I can answer my own questions.
- Currently there is no option to disable this feature, but it would be great to have it, saving bandwidth, disk space and preventing the inactive shortcuts list from growing. It's worth mentioning that Vivaldi uses a newer Chromium version (150) and doesn't auto-add search engines, so the Opera dev team could add this option.
- Not skipping inactive engines is considered a bug by burnout426, they assigned RNA-3999 ID for this bug, and said it's fixed internally. Unfortunately there is no mention of this code in recent changelogs (v133, v134, v135), so I guess we need to wait for this fix reach developer release and even longer for stable release (the one I use).
My Opera version is now 133.0.5932.60, and the bug still persists.






