I could reproduce the problem on my XA2 with ER78. To fix it, as nemo/defaultuser open the browser from terminal with a second tab, e.g.:
$ sailfish-browser about:mozilla
From the tab view you can now close the first tab without opening it.
I could reproduce the problem on my XA2 with ER78. To fix it, as nemo/defaultuser open the browser from terminal with a second tab, e.g.:
$ sailfish-browser about:mozilla
From the tab view you can now close the first tab without opening it.
Thanks very much @martinh ! Your hint worked. Browser is back again!
I did so how you wrote but out of confusion i typed ‘sailfish-browser about:settings’ , but despite my error browser opened, i was able to close both the former crashed and also the yellow framed 'not existing ‘settings’ tab.
Q: Is update to ESR91 possible on 32 bit devices (Xperia 10)?
It will be available with SFOS 5.0 AFAIK
You an submit these to the Sailfish OS Browser.
They can be added in the file below:
Is there any way to debug a site in the browser, like javascript console output or something similar?
I am using clozemaster.com for language learning and the “Next” button does not work there when playing a collection. It triggers a js event, so I wanted to look for any clues.
Please see this article:
Thank you! That was pretty easy to solve. Got the following from the console
[JavaScript Error: "TypeError: window.speechSynthesis is undefined" {file: "https://www.clozemaster.com/packs/js/850-853f2d39ddd52393a868.js" line: 2}]
setting “media.webspeech.synth.enabled” key in about:config, made the requested object window.speechSynthesis available in the browser
I can now finally ditch the android app.
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
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.
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.
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
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.