I am using C2 as a daily driver for multiple weeks now.
I have to say thank you again. The browser works great. I do not experience crashes anymore.
I hope for a second season on the gecko dev diary 
10 Likes
Has anyone else had any problems with searching after updating to ESR91?
Using the URL bar for searching leads to “invalid URL” error message. I have tried all the possible search engines, but the problem persists.
I’m using a fresh installation of SFOS 4.6.0.15 on 10 III. When I start the browser from CLI and do a search, this is what I see in the output:
JavaScript error: resource://gre/modules/SearchService.jsm, line 205: NS_ERROR_UNEXPECTED: SearchService previously failed to initialize
Is there something I could try at this point? Resetting the browser didn’t help.
Btw, update went smoothly on 10 V!
Is this still maintained and if so is there a possibility to update the browser engine like reapplying the install process?
Your choice. Either wait for 5 to arrive for Xperias too or install packages yourself in CLI.
That was misleading sorry.
I meant Flypig’s release package (gecko-dev-esr91-release.tar.bz2) is still the same as a few month ago and I verified it, it is.
My question is if version 91 is still under development and if so is there an updated package of it.
There was a mention of a browser engine update done in the release notes of the latest SFOS 5.0 update for the C2, so I guess the ESR91 browser is now being maintained as a part of SFOS 5.0.
Which of course means that those of us on non-C2 devices will have to wait for SFOS 5.0 to land on rest of the devices. In the most recent community newsletter it was communicated that their target is to release version 5.0 for all supported devices at the same time the next OTA update for C2 is released - no planned date was announced, however.
2 Likes
That was my guess as well after a while.
No. You can install it regardless.
It can be installed but is from last year and thus the up to date version is in the official tree now and will come out with an update.
1 Like
Just to confirm, ESR91 is now being maintained by Jolla and the official version has many improvements over the RPMs I provided earlier. Nevertheless I’ve been using those older RPMs on my Xperia 10 III with 4.6 for a while without problem, so they should still work.
@hschmitt: thanks for the kind words, which are also very motivational! I am planning a second season (102.15 being the next target) but have so far put off thinking too hard about it until at least after FOSDEM this weekend 
45 Likes
I mean that is so cool! Just reading the diary was interesting all the time, not to talk about finally having somewhat of a working browser.
4 Likes
@flypig let’s figure out a bit of plan regarding 102.15. It would be great to team up maybe with @mal and myself. At least we should align our thoughts.
21 Likes
102.15 esr would be a huge step in the right direction, like esr91 already is.
I am not a coder, so I don’t fully understand how much effort it takes to port to never versions, but the browser is unfortunately the biggest issue in terms of security, and having a current version would be a big improvement, not only to have better website support, but also to close a lot of security holes (Backporting security fixes is not feasible for web browsers, even Debian stopped this years ago).
SFOS 5.0 is out and it is said that this browser has to be uninstalled first.
Maybe you had a look some post above and found this:
So the updater find a older package of the browser files but unknown in the official list. And so the updater ask the question you see.
1 Like
Sorry, wasn’t a question but just a note to anyone wanting to update. I uninstalled the packages and reverted the browser to it’s original state as mentioned in Flypig’s website.
1 Like
Thanks for reporting, I can reproduce this as well. We’ll look into it.
5 Likes
I upgraded to SailfishOS 5 now and I am trying to adapt the patch Browser history swipes. I see one change in ToolBar.qml, toolBarRow.width is changed to toolsRow.width (it is under id: touchArea - line 306) and second change is in PopUpMenuFooter.qml - there is removed id from forwardButton (around line 40). I made changes in the patch and swipe back gesture is working now but swipe forward not, I need more investigation.
3 Likes
Please release it when fixed
Really love this patch! It already stopped working at some point in the past for me. After the first release of esr91 it still worked, then after another release I couldn’t apply it anymore.
1 Like