Comment by Slartibartfass
I know it is a duplicate but it seems, the other posts are forgotten. I recognized the update from 38.0 to 45.0 with Sailfish OS 3.1, but that is not enough in 2019.
View ArticleComment by Slartibartfass
No, i did not know, that i can reopen an existing post. But I suggest, it will be the same as here: Instead of updating, the discussion switches to how communicate better. It think, it it the job of...
View ArticleComment by Nautilus
@Slartibartfass They are not forgotten. As evident from IRC meetings, Jolla has an internal roadmap on updating the browser, they just won't make this roadmap public. Having multiple posts on the issue...
View ArticleComment by Spam Hunter
Then reopen/edit the last post on the subject!!, this is why subjects get diluted and votes become harder to collect, stop spreading the same crap all over the entire forum Don't people realise they...
View ArticleComment by Spam Hunter
It is most certainly a duplicate many times over, and should be closed as such. Another user who refuses to check before posting *sigh*
View ArticleComment by Spark
It's a duplicate, but since this topic is timeless at Jolla I don't bother having one more reminder. Upvote!
View ArticleWhen can we expect an actual web engine?
The web browser of Sailfish OS is very old (Engine 3/2016 in 3.1.0.11, the actual stable release)> "Mozilla/5.0 (Linux; U; Sailfish 3.0; Mobile; rv:45.0) Gecko/45.0 Firefox/45.0 SailfishBrowser/1.0"...
View Article
