29
Merged 1 post from Kagi Assistant does not load correctly.
    12 days later

    Opening kagi.com/assistant with minimised left panel leads to text overflow. See screenshot.
    Browser: Firefox 115.15.0esr (64-bit).

    Text should not overflow.

      EDIT: I thought this report was related to another one but it doesn't seem to be the case.

      Could you please share which browser you're using?

        Hi Luis, I'm using Firefox 115.15.0esr (64-bit).

          legeana to resolve this problem, I recommend updating your Firefox ESR version to the latest available. After the update, you should no longer encounter this particular issue

              I saw a better suggestion to use https://kagi.com/v1_assistant instead.
              I don't have an option to upgrade Firefox right now, thank you. Feel free to mark this bug as a duplicate.

                Merged 7 posts from Minimised left panel leads to text overflow.
                  6 days later

                  Debian stable-security repos started shipping Firefox 128 ESR on October 2, so those of us using Firefox from Debian stable can now use the new assistant after a system package upgrade. It works for me!

                  I agree with others in this thread that a mature web engineering org will have a legible browser support policy. Kagi may not be there yet, and that's fine. When you do get there, I hope you'll include Firefox ESR (according to Mozilla's release policy).

                    I tried opening the link to the Assistant in MenubarX browser on my mac (which offers an easy way to access instantly with a shortcut, great for fast browsing or pinning a small window)

                    Anyways, the Ai Model selection keep Loading, but it never loads, and my History Threads aren't shown

                    I did try "deleting site data" in the browser, I also tried changing the User Agent & Window Size, but nothing works.

                    FYI, I did use MenubarX successfully in the past with ChatGPT, Claude, & Perplexity.

                    I expected site to load correctly, so I can use it.

                      Merged 1 post from Can't load the Assistant in MenubarX Browser (MacOS).

                        Hello everyone, we are addressing these compatibility issues. We will keep you updated in this thread.

                          a month later

                          I'd like to offer up a plea... this is to Luis, David.... and to all the other truly esteemed development folks at Kagi:
                          Since this Firefox Version 115ESR page rendering issue is still being 'addressed', any chance I could get you to consider extending the 'Sunset' date for this V1 page:
                          https://kagi.com/v1_assistant?mode=7&sub_mode=2
                          ... from (YIKES!!!!) tomorrow (Nov 12, 2024), to a date further out into the future...
                          This way, while you continue to address the backwards compatability issue, I can continue to use this page, for my AI queries, on my work Windows 7 PC, which has Firefox 115.17.0ESR installed (adn where they won't let me install other browsers).
                          I'm on bended knee, begging at this point! Please, and...
                          Thanks!
                          🙂
                          Chris

                          • Luis replied to this.

                            cmart
                            On my home computer, which is Windows 10, I upped to 128ESR, and so for that PC, voila problem solved! But here, on my work PC, it's all about Windows 7 (which... hey... it's still a great OS, even though end of life and all that). 128ESR and Win7 (unlike Hostess and Kids)... just don't go together. So, I'm pretty much depending on the V1 assistant while Im' at work. And thus, I really don't want to see that "Sunset" happen to the V1 assistant page...

                                NOVALLY we will extend the deadline until we resolve support for older browsers

                                    Thanks, Luis. I did have a bit of a realization this afternoon on my home (WIN 10) PC, and this hint might help some others. I'm on Firefox 128.3.1ESR at home. And initially, when I went to the new assistant page today (https://kagi.com/assistant), I was having the same issue I'm having on work PC (Win7, FF 115ESR). I then dug into my config settings, and lo and behold... found one particular setting related to popovers which I'd turned off:
                                    dom.element.popover.enabled (I had this set to False --- likely one of many 'lockdown' settings set in the past to limit outside website influence).
                                    Well, the second I changed this back to TRUE ---> the new Kagi assistant page loaded 100% perfectly. Now works like a charm from home. So yeah... this makes me wonder if my work FF might have similar prefs set. Won't know on that until Monday, but... worth a shot. Oh, and I did find a few other prefs (some old/legacy) I may need to trial and error at work. (In case these help anyone else):
                                    dom.enable_web_api_popover | true
                                    browser.popovers.enabled | true
                                    ui.popovers.enabled | true
                                    .
                                    Thanks again for keeping V1 sunrised until this older browser compatibility stuff is ironed out.

                                    Luis, all...
                                    For the record, back at work, on my Windows 7 PC, which is running Firefox 115.17.0esr, I tried turning all of these preferences on (setting them to TRUE):

                                    dom.element.popover.enabled (this is the significant one, and was also set to FALSE on work PC)
                                    dom.enable_web_api_popover (wasn't present)
                                    browser.popovers.enabled (wasn't present)
                                    ui.popovers.enabled (wasn't present)
                                    javascript.options.experimental (wasn't present)
                                    dom.enable_popup_management (wasn't present)
                                    dom.webcomponents.enabled (wasn't present)

                                    The results? Still not functional, but closer. I can minimize or expand the sidebar thing. Also, because I'd set my default AI provider in the dropdown, from home yesterday, I'm seeing that today (instead of just saying loading forever), so that's good.
                                    But the biggest stopper is that I can't "X" out of that disclaimer in the lower left. So when I try to type in something in the prompt box, it just vanishes away and takes me back to a blank search prompt box.
                                    Below are some screen shots in case they might help...

                                    23 days later