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
Same here - searching via url bar does not work anymore
@flypig first thank you for your efforts in upgrading the browser engine! I have a question that might be silly or not: if it takes months / a year to jump from one ESR version to the next (which is understandable), how about skipping the next and immediately jumping to the latest ESR? So from v91 straight to v128 - maybe that would be an extra 10-20% of work, but probably not 3x100% of work because of 3 jumps (to v102, then to v115, then to v128). What do you think?
1 Like
This is explained in the blog.
Why would you think that obvious things like that have not been considered? 
I doesn’t sound like you have any personal experience in the area…
You do not need to have personal experience if you are explained to you by a knowledgeable person. That said, I know that flypig has already explained this matter.
1 Like
No; but personal experience not lining up with the chosen process, or previous explanation, would be a good ground to question them on. Assuming people complicate basic things for no reason is not.
of course I will release it if I get it fully working
Did you set search engine in browser settings?
Yes, i did
20 characters
I had that problem too, but after I set search engine to duckduckgo, searching via url bar works.
2 Likes
What I was trying to say, as I know you are a knowledgeable person, was that you could try to explain (or link the explanation) instead of just dismissing everyone, in the way you tend to do.
No hard feelings, It’s just my usual outspokenness.
2 Likes
My search engine is set to duckduckgo. I even changed it twice but that did not help