Internet broken by design.
1 Like
I found myself thinking that OTOH, these kinds of things are the only ones really forcing development priorities to shift and hunt for additional resources. We might otherwise be stuck on ESR78 for another decade.
It is always positive when something that is so behind the “current” versions of things get updated even a little bit, and I’m happy for the upcoming update. I just don’t want to people to think this is some kind of magic bullet that solves the issues with Cloudflare.
When comparing how long it took to get from ESR 78 to ESR 91, and how fast the ESR 102 is coming out after ESR 91, it is a positive surprise at least for me. With this rate we might catch relevant (actively supported) version of ESR in couple of years.
6 Likes
Let’s hope that Jolla will keep this phase or even accelerates the development! Catching the supported version would be so great
For the sailfish browser (whichever version) it is easier to maintain a list of sites that do work. As long as you can get aurora or f-droid and have app-support you do the usual sailfish-thing … work around it!
Did Twitter stop working for anyone else?
Edit: nevermind, my problems don’t seem isolated to ESR 91
To clarify, esr102 is very far from being release ready. I see it very unlikely that it would hit the first Sailfish OS 5.1 version. What’s good is that it can be rather easily be pushed to 5.1 update release when it is release.
Please see also Community meeting on 22nd May 2025
3 Likes
Good clarification, as non tech person it is hard to estimate the amount of work still required. But definitely good use of the resources to push the browser to be up to date once again. Of course it will take time which is understandable.
2 Likes
Rule of thumb: The last 10% of the work takes 90% of the time.
Let’s hope, that Jolla is already in the last 10% of the work.
3 Likes
These sites report an outdated browser and do not show anything else but the warning:
https://www.bonjour-ratp.fr
https://compte.bonjour-ratp.fr
So, there seems no way to use the phone (JollaC2) for public transportation in Paris.
On my Xperia 10 II, these sites display a warning the first time they load. But when I reload the page, they render correctly.
Reloading the page(s) helps, indeed.
2 Likes
This works for me on an X10III.
The other site is the same for other users.
Can’t login to Wise account in the native browser at https://wise.com. It leaks so much that it gets killed after loading the front page.
Restarting Home screen is not enough to clear a decent amount of RAM, a restart is practically required on my XA2 after just one attempt. I’ve recently flashed Sailfish OS 5.0.0.67 on it.
https://www.eventim.de/artist/linkin-park/linkin-park-from-zero-world-tour-2026-3913758/
or
http://www.eventim.de/event/linkin-park-fromzero-world-tour-2026-allianz-arena-muenchen-20331402/?
Access Denied
You don’t have permission to access “http://www.eventim.de/event/linkin-park-fromzero-
world-tour-2026-allianz-arena-muenchen-20331402/?” on this server.
Reference #18.24851502.1749144948.4ff45a9
An error has occurred
For us homelabbers: Grafana is not working with Browser. Shows the jumping Grafana logo at first for a few seconds but then gives the generic error:
Would be nice to have a dashboard for mobile use to just check some basic stuff at times.
The site works elsewhere on the same network, and toggling desktop mode does not help.
Their support page doesn’t really help: Install Grafana | Grafana documentation
1 Like
Youtube shorts
Sigh, again, youtube shorts are so laggy they are unwatchables 90% of times
Instagram videos
That too, they are so broken they are unwatchables 99% of times, it’s very rare to find a video which is watchable…
Jolla & Sailfish OS should get themselves listed on Browserslist & Caniuse so developers can be wary of skipping out on supporting this browser. I have added Firefox 91 to my own targets, but I highly doubt many others will as well. Some things like JavaScript are easy to compile down to something that still support Fx91, but some of these new CSS features are hard to detect & nearly impossible to polyfill reasonably. As a user, you can start enabling flags with the user.js file like the <dialog> element, or in my case, setting the user agent to a new Firefox due to sites like Shopee (online shopping, multinational) doing UA detection despite it being known to be a broken practice.
3 Likes