-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chromium no default search engine set #2
Comments
Does it work on a Chrome browser for you? |
Same here, no default search engine set whatsoever. Linux, Chromium 109.0.5414.119 snap |
You can check instrucitons from Kagi docs to set it manually https://help.kagi.com/kagi/getting-started/setting-default.html |
Chrome doesn't support it yet, though the code will enable it once it does. |
It might be worth updating the documentation here: https://help.kagi.com/kagi/getting-started/setting-default.html#browser_extension
I see now that the docs later link to the manual setup under chromium, but it would be good to rephrase the initial paragraph to something like:
That nudges folks to read further. |
@gauntface Thanks for the heads up. As a note, all documentation is open source and editing is as easy as clicking the Edit link on the bottom of the page. |
@vprelovac ah thank you - ❤️ that. PR coming soon. |
Hi all - we took a quick look into this, it seems that with Chromium on Linux, it no longer works; it seems to have broken since we launched the extension. It is not clear whether this is a regression or intentional change in Chromium. It still works on Chrome on Windows. Other extensions (e.g. DDG's) also appear to have broken for this use case. |
Interesting. Indeed it looks like a regression on their end, given https://developer.chrome.com/docs/extensions/mv3/settings_override/ . Can someone test this on macOs? |
Actually, I misspoke. In the latest version of Arc (1.21.2) the Kagi extension does successfully set the default search engine. It messes up the Arc UI a little bit, as it shows a blank entry in the dropdown for the default search engine. However, it does seem to work. The manual configuration as per the docs does not work. |
Yup, on Linux using Chromium, the extension fails to change the default search engine to Kagi. |
@yammesicka thanks for this tip! I think that should be added to Kagi docs and/or handled by the extension in the future. |
it fails in windows too now using brave browser. No idea what to do. |
Hi @coccigelus can you please give us some details of your system? I wasn't able to reproduce: |
Hey, after installing the extension, it did grab the session but no default search engine was set.
System:
Version 107.0.5304.110 (Official Build, ungoogled-chromium) (64-bit)
-> Installed with flatpak https://flathub.org/apps/details/com.github.Eloston.UngoogledChromium
Extension version 0.2
Am I doing something wrong?
The text was updated successfully, but these errors were encountered: