Assistant page don't load correctly on Firefox ESR 115, librewolf
Ever since Kagi Assistant became the new AI interface, I haven't been able to load the interface on my desktop. Buttons do not work, typing a query and pressing enter just makes it disappear into the void. I've cleared cache many times and tried private browsing mode. OS: Debian 12.7, Browser: Firefox 115.15.0esr (64-bit)
I expect the interface to load correctly.
elpFXcrbFw this can be resolved by updating FF to the latest release (https://packages.debian.org/stable/web/firefox-esr)
- Edited
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).
Looking at other issues I found https://kagifeedback.org/d/4726-assistant-page-dont-load-correctly-on-firefox-esr-115-librewolf which is what I'm dealing with.
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.
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.
Hello everyone, we are addressing these compatibility issues. We will keep you updated in this thread.
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
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...
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.