Hey fediverse--

I recently made the switch from desktop Chrome to desktop #Firefox, which has mostly been fine, except for one problem:

Firefox stops bothering to answer AJAX requests in tabs pretty quickly, which makes my preferred webmail client--#Roundcube--FAR less functional under FF than it was under Chrome.

If left alone for a moment--or sometimes, even while typing an email--FF stops paying attention, further AJAX calls fail, and I'm forced to refresh the tab.

Anybody have any ideas?

belated note: I'm running Firefox on Ubuntu 26.04, using the default snap. (Pic related.)

I don't think the problem is localized there, though, because when I went a-web-searchin' I saw MANY similar complaints about Ajax and FF dating back nearly 20 years.

On a suggestion from someone who says they have no issues with Roundcube under Debian FF ESR, I tried installing from Mozilla's Apt repository.

No obvious change, sadly. Still gets stuck on "refreshing" and fails to update.

@jimsalter I would look in the web inspector and see what happens when it tries to make that request. It will show an error that may or may not be useful. I suspect that their auto refresh mechanism first calls some kind of analytics request first, and Firefox is blocking that for tracking protection.
@nyquildotorg these are the warnings I'm seeing. Not seeing anything labeled an "error."

@nyquildotorg it just took upwards of 30 seconds to complete one of those "Refreshing..." loops. No additional warnings appeared.

I've never seen it take longer than MAYBE 500ms in Chrome. Usually, more like 50ms, barely enough to spot before it's done.