Browser Compatibility Request - Firefox ESR 115.24.0 on Windows 7 - Dropdown Menu Issues

NOVALLY

Kagi Support.
This issue is related a bit to a post I submitted back in 2024 (this one):
https://kagifeedback.org/d/4726-assistant-page-dont-load-correctly-on-firefox-esr-115-librewolf
I'm still on the same Windows 7 Pro PC at work (if only it didn't work flawlessly, I could get it replaced).
My issues now are related to accessing the Settings dropdowns using my Firefox ESR 115.24.0 browser (last version that works with Windows 7)
When I try to access any of these SETTINGS pages (which have dropdowns), like these:
https://kagi.com/settings/general
https://kagi.com/settings/appearance
https://kagi.com/settings/search
https://kagi.com/settings/assistant
etc...
I cannot activate any of the dropdowns to see and select what's inside those dropdowns.

Pretty sure this is because Kagi's relying on setPointerCapture() and releasePointerCapture() APIs for functionality. Firefox 115 ESR's internal dropdown handling still uses the deprecated Element.releaseCapture() method.

My hope (plea) is that maybe the devs there would be willing to write in some backwards compatibility accomodations to help me to get to these dropdowns from work.

A few possible solutions:

(a) Fallback dropdown implementation for older Firefox versions (like mine, which use traditional mouse event handling instead of the pointer capture APIs)
(b) Polyfill integration (so as to provide missing pointer capture functionality for legacy browsers like 115.24.0)

I realize 100% that adding in code for "dinosaur" configs like mine isn't the most hot or urgent stuff on the TO DO list, but I'd just like to have some fallback to let me get into these settings from work.

Anyways, thought it would not hurt to plead my case, and ask!
Thanks for at least reading this (and hopefully, helping an Early Adopter loyal user out!)
😉

to have dropdowns work in my legacy Firefox ESR 115.24.0 browser (as explained above).

Thibaultmol

Some changes were deployed today that affects the accessibility of the settings page in particular. Did you start noticing these problems today or before that?

NOVALLY

Thibaultmol
I'm going to go with today. I think last time I was in 'Settings' from here was on Monday/Tuesday... and now that I think about it... yes, dropdowns worked fine then.

jacobwinters

Looks like the root problem is that we're using the Element.ariaExpanded property, which was added in FF 119, to write to the DOM when you open a dropdown. In FF 115 the write fails silently. I'll change the code to use the older get/setAttribute APIs.

More immediate fix: The noJS version of settings at https://kagi.com/html/settings should already work in FF 115. (The region and language dropdowns look a little broken in noJS mode. Despite appearances, they do, in fact, work. Appearances will be fixed shortly...)

NOVALLY

Very much appreciated. And thanks for the noJS pointer!

NOVALLY

.... continued....
Just realized on the main Kagi search page https://kagi.com
... the four dropdowns there also won't trigger with FF 115. As in these: https://imgpile.com/p/GMVLyd0
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
The short term fix here? By going here https://kagi.com/search
... I'm good (those dropdowns work).