Posts: 14
Threads: 5
Joined: Jan 2025
01-20-2025, 03:22 AM
When I enable the "Show search box" option in "New tab page", it will always use some default search engine instead of the search engines I have installed and set as default:
Even removing these search engines in
chrome://settings/searchEngines it still doesn't get removed from the search box and my default search engine still isn't used if I do a search using the search box.
I hope the update to the search box will only use the search engines that the user has installed and set as default, instead of always using these default search engines.
Tell me I'm your national anthem
Posts: 6,207
Threads: 90
Joined: Oct 2014
Currently the search list here is fixed, we will consider improving this feature in the future.
Posts: 14
Threads: 5
Joined: Jan 2025
(01-23-2025, 05:12 PM)Admini Wrote: Currently the search list here is fixed, we will consider improving this feature in the future.
Also, when I remove the default search engines at "
chrome://settings/searchEngines", it will be saved to the "
User Data\<USER>\Web Data" file. However, for some reason, this "Web Data" file will cause the passkey feature of the Bitwarden extension to work erratically after every browser restart. But simply deleting this "Web Data" file will make the Bitwarden extension work normally again.
I hope you also move the data when removing these default search engines to another file.
Tell me I'm your national anthem
Posts: 6,207
Threads: 90
Joined: Oct 2014
(02-01-2025, 09:07 AM)tanquang Wrote: Also, when I remove the default search engines at "chrome://settings/searchEngines", it will be saved to the "User Data\<USER>\Web Data" file. However, for some reason, this "Web Data" file will cause the passkey feature of the Bitwarden extension to work erratically after every browser restart. But simply deleting this "Web Data" file will make the Bitwarden extension work normally again.
I hope you also move the data when removing these default search engines to another file.
Thanks for your feedback.
Have you tested this case in Google Chrome?