111–120 of 158 posts
Earlier quoted context omitted.
There could just be a difference in hardware. I'm a Firefox user but there is a noticeable difference, just not one that matters much on a top tier soc
Loading JS heavy pages like Twitter on Firefox Android is way slower than Chromium based. Very noticeable on 2019 hardware, less so but still on 2022 hardware.
This is an exhorbitant exaggeration. They are duplicated requests for a favicon. Not only is that a tiny resource, most of these requests are 404ing which is cheap. And even if it isn't 404, your favicon is a tiny static asset, it should either be served by CDN or in the server's filesystem cache anyways.
I thought firefox on ios was just safari with a reskin because apple doesn't allow other browser engines on their phone? Firefox on android is amazing with its plugin support, though I still prefer their pre-2021 UI
Firefox on Android is not amazing, it is on the contrary quite annoying and has gotten more so over the years * Tabs get stuck frequently, and can only be revived by closing, then undoing close. * Can no longer access about:config in release builds * Bookmarks got demoted in favor of Pocket, can no longer set bookmarks as default home page * URL autocompletion got dumbed down, first on mobile and then also on desktop…
I thought firefox on ios was just safari with a reskin because apple doesn't allow other browser engines on their phone? Firefox on android is amazing with its plugin support, though I still prefer their pre-2021 UI
The author of this site usually takes pains to obfuscate whatever big commercial entity she's talking about who did dumb stuff. But when it's Firefox, she names names. Huh.
The author of this site usually takes pains to obfuscate whatever big commercial entity she's talking about who did dumb stuff. But when it's Firefox, she names names. Huh.
Earlier quoted context omitted.
In this case, using a CDN in front of the server is the thing which would improve things for people with limited bw/hw more quickly and to a greater extent than counting the fetches by Firefox on iOS and calling it out for fetching too much
But if clients were considerate, we wouldn't need to waste electricity and work hours to run CDNs?
Earlier quoted context omitted.
> Having a path-specific favicon actually sounds like a feature. Can you provide at least a couple of use-cases for a path specific favicons?
Sites where users each get a directory for their profile.
Is that also the correct behavior for trying to identify a favicon for something like docs.oracle.com/javase/8/docs/api/org/xml/sax/helpers/DefaultHandler.html