3

Steps to reproduce:
-Install Kagi Search Extension
-Select Kagi From Drop-Down Menu in Search Field

Expected behavior:
Expected to See the Kagi Icon in the Search Field

Debug info:
Vivaldi 6.2.3105.48, Search Extension Version 0.3.7, Debian 12, US-CENTRAL

Image/Video:

    I restarted my browser & the extension I removed came back, & the icon was gone again.
    This time when I removed the extension it stayed gone, but so did the icon.

    After several browser restarts the extension remains gone, but the icon didn't come back.

    I had to remove the Kagi from default everything so that I could remove it from the list of search engines, & re-add it manually yet again. Only then did the icon work again normally.

      So it seems to be sketchy how the icon is displayed or not. Not sure why but after this particular reboot the icon is no longer displayed, I imagine I'll have to remove & re-add the search engine to the list again to get it to display properly which is really not worth it to me anymore. So I will not have an icon.

        @NginUS Is this possibly a bug in Vivaldi? I can't replicate this on either Chrome or ungoogled-chromium. Manually setting search engine or using the extension, I get an icon....
        (N.B. With Vivaldi based on Chromium codebase, I assumed any bug "upstream" would be found there, too.)

        Thanks, it does appear to be a bug in Vivaldi. Are there any search engine extensions that correctly dispaly this in Vivaldi?

          Vlad
          None of them create an entry in that drop-down menu afaik, I tried a half dozen of them

            Has anyone been able to reproduce in a Debian 12 VM with a current Vivaldi? I installed from a current netinst .iso not too long ago in case that might be of use.
            Alternately, is there anything I can do to help diagnose or otherwise help? As I mentioned, trying a half dozen search extensions didn't help any because none affected the relevant field.

              2 months later

              Appears to be solved as of version 6.4.3160.44, through multiple application close/launch cycles, even survives a reboot so far.

              No one is typing