Assistant page don't load correctly on Firefox ESR 115, librewolf
- Edited
- While logged in, browse to https://kagi.com/assistant.
- Notice the model drop-down menu (just below the prompt input) reads "Loading..." (and never finishes).
- Clicking the "X" for the "Private by default" pop-over does nothing.
- Browser console shows "Uncaught TypeError: Ur.showPopover is not a function"
Attempting to enter and submit a prompt does nothing in the UI, but results in a different console error:
Yes, Firefox 115 is not the latest, but it's still a supported ESR release that gets security updates. I use it because it's default browser on Debian stable.
And yes, I have JavaScript enabled
Assistant works as expected in Chromium 128 on the same computer.
I also have this same issue. Model drop down stuck on "Loading...".
I'm on debian trixie/sid with firefox 115.15.0esr-1.
I can confirm chrome works too.
Steps:
- In Safari, load the assistant
- Press the button marked "Claude 3.5 Sonnet"
Actual:
- A modal is displayed with the words "No results"
Expected:
- A list of models appears to choose a different LLM model
Confirmed that it works in Chrome.
Hey Ben,
which version of Safari (and macOS) is this happening on? Do you have any browser extensions installed?
I am unable to reproduce the issue on macOS Sonoma 14.6.1 running Safari Version 17.6 (19618.3.11.11.5)
- Edited
I was running 1Blocker and StopTheMadness but I'm still seeing it after disabling both of those. Let me know if there's anything else I can do to help debug.
Update:
I tried this in Safari 16 in BrowserStack and in that case the list doesn't load at all:
And Safari 17.3 in BrowserStack:
Unhandled Promise Rejection: TypeError: Object.groupBy is not a function. (In 'Object.groupBy(w,e=>e.id?"customAssistants":e.model_provider_name)', 'Object.groupBy' is undefined
Looks like groupBy wasn't fully supported until 17.4:
BenJohnson
Thanks for digging deeper. Indeed, older versions missing some features seem to be causing issues. This is very similar to #4726 and unfortunately the only remedy for now is to install a more up-to-date version of Safari.
Kagi should have a clear policy of how old browsers they support. This is a very common problem within the industry.
In this case they can either polyfill groupBy or write the code differently.
The problem with Safari is that you can’t just ask users to update. The versions are bound to OS version. So for instance, a lot of users are on old iOS devices, locked to Safari 12, which is really old, and Kagi should strategically decide if they want to support these users or not. It is possible, just a bit of extra work.
- Edited
laiz @BenJohnson Yes. I'm merging this thread with the other since both report the same problem, and the other thread has further details and follow up discussion
Just open kagi.com new assistant And it will show broken page, javascript error, and nothing works on this page as a result.
I'm using Waterfox G6.0.19 (64-bit) on Mac OS.
Working assistant
I'm seeing the same thing in both Arc and Safari. I've tried disabling extensions, but that doesn't help. I did get one query to go through in Safari, but then I've gotten the message
Something went wrong while trying to get you your response
for every other query I have tried.
I'm experiencing this issue on Firefox 130.0 (Installed via Snap on Ubuntu 24.04).
Hopefully the assistant comes back up soon
- Edited
Adding the following polyfill may solve it:
https://github.com/oddbird/popover-polyfill
Also seem to remember something about group by, then you can add:
Cannot use Kagi Assistant on firefox linux. It just doesn't load the models and the ui gets broken.
It also is impossible to interact with the entire left pannel
Cannot access Kagi assistants : this error causes AI models list to not load, and other UI issues, making it impossible for me to use Kagi assistant on firefox on ubuntu.
showPopover seems to be a fairly recent api, available in Firefox releases after April. Not untypical that e.g. Debian releases, are a bit behind, iirc.
It can most likely easily be fixed by adding a polyfill (https://github.com/oddbird/popover-polyfill).
Although it is nice to use recent js APIs, I think it would be beneficial to support some later versions of browsers. At least be very clear about what you support. Ideally telling users when they are on unsupported browsers/versions.
https://caniuse.com/mdn-api_htmlelement_showpopover
I would expect older iOS devices to struggle with this as well. And not all iOS users can upgrade.
I guess assistant is relying a lot on client side js, while search is not. I’ve seen several threads on similar problems.