REPRODUCIBILITY: not sure
OS VERSION: 5.0.0.68
HARDWARE: Xperia 10 III
UI LANGUAGE: English
REGRESSION:
10 Likes
There will soon be a browser update
1 Like
Search before posting.
1 Like
Duplicate!
Workaround for the moment would be possible: use Firefox or Fennec from F-Droid.
But beware of Fennec v. 142, install v. 141 manually. The latest version has a bug at the moment, but they’re working on it.
Or maybe you can edit the User-Agent string in about:config to fake a newer version and get rid of the message until ESR 102 arrives.
IMHO forum maintainers should remove that warning.
3 Likes
Although there is a duplicate, the irony in this situation is so funny I still enjoy it.
11 Likes
The ESR 102 is already over 3 years old. This should buy us a few more months until more sites stop working again. I hope Jolla will skip 115 and 128 and start working directly on ESR 140.
1 Like
This has happened at least twice before, and never developed into an actual issue.
Skipping too many releases means potentially getting a too big diff to apply the required changes to. So unless you have a more substantial argument than “more higher version number, more good“ do consider leaving that to the actual developers.
5 Likes
Which is what I did. I did not say “They should do this and that.” I said, “I hope,” which factors in that the decision is theirs. But the hope is mine.
2 Likes
It was explained here why jumping to the latest-and-greatest (while it sounds like a good idea) is not a good idea after all.
I also picked some quotes from the blog that flypig has.
'As a result, to get through a full build it generally needs to be cancelled and restarted multiple times. Gecko supports incremental builds, so it’s not as painful as it would be otherwise, but it still makes it hard to determine exactly how long a full build takes. In my estimation it’s between five and eight hours on my development machine (14 cores, 16 threads, 32 GiB RAM).
Upgrading gecko for Sailfish OS is a big job. Just checking the git history I can see that the upgrade from ESR 68 to ESR 78 took in the region of nine months work from a team of contributors. Like I said, it’s a big job.
8 Likes
I just hope that after esr102 release Jolla will still keep prioritizing the native browser and start to work on next step. Good browser allows people to use the phone much more and might be critical to many. I would hope that community could contribute at some way and speed up the development.
11 Likes
With an up-to-date browser one needs less Android apps. So yes, this should be one of the most important developments.
21 Likes
This forum issue is duly noted.
17 Likes
Is flypig still around?
2 Likes
Yes, still around! But I’ve been a bit distracted with other (Sailfish OS-related) things recently.
16 Likes