SUMMARY *** No matter which search engine I select, search is always done through DuckDuckGo. *** STEPS TO REPRODUCE 1. Edit/Preferences/Other/Manage search engines/Search Engines Manager 2. Move google to top 3. Select google as default 4. Apply changes 5. Type any non-URL text in the navigation bar (I tried just "KDE") OBSERVED RESULT A DuckDuckGo search page is displayed EXPECTED RESULT A Google search page is displayed SOFTWARE/OS VERSIONS Plasma Version : 5.24.5-2 KDE Version : 22.04.1-1 Frameworks Version : 5.94.0-1 Qt5 Version : 5.15.4+kde+r1-1 ADDITIONAL INFORMATION n/a
Seems to work for me if I write "g:test" to search "test on Google Tested in latest KDE Neon testing with: KDE Plasma version : 5.24.90 KDE Frameworks version: 5.95 Qt version: 5.15.4 Kernel version 5.13.0-44-generic
Of course "g:test" **explicitly** invokes whatever search engine is configured for "g". What if you type "test" in the blank address after having followed the "STEPS TO REPRODUCE"?
you forget a step: go to Edit/Preferences/Tabs -> Address Bar Behavior and Tick box 7 "Search with Default Engine" and now it should work as expected, if so please mark that as resolved
It works! But is also keeps working after having reset that toggle, while it shouldn't. What is the intended meaning of that "Set as default" button in the "manage search engines" window?
BTW, my current setup is: Plasma Version : 5.26.2.1-4 KDE Version : 22.08.2-1 Frameworks Version : 5.99.0-1 Qt5 Version : 5.15.7+kde+r5-1
Falkon is v22.08.2
> What is the intended meaning of that "Set as default" button in the "manage search engines" window? I can only try to guess. My usecase is to have the URL-bar as well as Search-bar in to toolbar at the same time. (I have URL field and search field.) The use of default in this scenario is, that I can have a defaut search engine invoked from URL bar and different one selected in search bar. Example: - Default engine is DuckDuckGo - In searchbar I have StartPage -- The option to use default engine in url-bar is set -- When search is invoked from url (adrress?) bar it will use DuckDUckGo -- The option to use default is not set -- When search is invoked from URLbar it uses the currently selected engine in the Search-bar which is StarPage So in my opinion it works as expected. We can get to some "uninformed" behavior like you did when the searchbar is hidden. From my experience the order of search engine has no effect on this (or it does and I am not aware of it) and is probably for pure cosmetic use in selecting search engine in Search-bar.
I see this as an over-complication in an otherwise clean browser. The browser has a "default search engine" setting. It should use it whenever and wherever it needs to do a non-explicit search. For searches on explicitly chosen engines the user should go to the relevant web pages. As a bare minimum "pseudo-fix" to this "bug" I would put that "Search with Default Engine" on by default. As a real one I would remove that toggle (and all related code) and would make Falkon use the default search engine everywhere. I would like to hear whatever idea the Falkon maintainer team has too, so I can better understand the philosophy behind it.
> As a bare minimum "pseudo-fix" to this "bug" > I would put that "Search with Default Engine" on by default. I can consider this for the next release. (I do not like configuring the default options.) > I would like to hear whatever idea the Falkon maintainer team has too, > so I can better understand the philosophy behind it. I can be considered as a maintainer at the moment and my idea is to leave it for someone who is interested to work on it. (in order to do it properly) To understand the idea behind this? It could be as I said before, to work better with search bar, but the correct philosophy is unknown to me, since I did not make this feature, I arrived here when the feature was already there. Maybe you can find something in the commit messages or in old Qupzilla issues, merge requests.
(In reply to Juraj from comment #9) > > As a bare minimum "pseudo-fix" to this "bug" > > I would put that "Search with Default Engine" on by default. > I can consider this for the next release. (I do not like configuring the > default options.) There are many already there... > > I would like to hear whatever idea the Falkon maintainer team has too, > > so I can better understand the philosophy behind it. > I can be considered as a maintainer at the moment and my idea is to leave it > for someone who is interested to work on it. (in order to do it properly) > To understand the idea behind this? > It could be as I said before, to work better with search bar, but the > correct philosophy is unknown to me, since I did not make this feature, I > arrived here when the feature was already there. The feature looks like it is either incomplete or wrong: default search engine is used differently in two places of the same application unless otherwise stated (by that toggle). > Maybe you can find something in the commit messages or in old Qupzilla > issues, merge requests. I would say that "common sense" should fill the gaps in the documentation. Either you use the default search engine everywhere or you let the user specify as many search engines as the number of places where it can be used. In this case, once for the search bar and one for the URL bar. Anyway, the "feature" is somehow broken. https://bugs.kde.org/show_bug.cgi?id=454398#c4 If you go to Edit/Preferences/Tabs -> Address Bar Behavior and tick box 7 "Search with Default Engine", even when you un-tick it back, the URL search engine stays in sync with the search bar one. Which is what I consider the way this feature should be. If you don't think this is a bug, then close it as "NOT A BUG" or "WON'T FIX". And, in any case, even as it is now, once you toggle that "" check box, you cannot go back to the previous behavior anymore.