Comment by bennypr0fane
Guys, would you give it a rest already with the arguing? I believe Jolla doesn't need persuading to fix this. I'm pretty sure this is not intended, but a bug. Update 10 was all about memory...
View ArticleComment by rdmo
This memory optimisation is not optmising battery life or an expected behaviour. It may have seemed a small thing but it interferes with the most basic and and equally more complex user intrractions...
View ArticleComment by foss4ever
Any news for getting this fixed now that the issue has reappeared in 1.1.1.27 ?
View ArticleComment by romu70
The problem of this tab freeing behavior is it prevents some mobile web sites to work. An example: Pocket. Pocket is opened in the tab A. Click on a link and assume this link is opened in a new tab,...
View ArticleComment by veskuh
@Setok Yes, that is being worked on. (You can even follow the progress in sailfish-browser's newWebView -branch)
View ArticleComment by Setok
Chiming in to say please, please, please at least remember the scroll position in back/forwards. The current behaviour is incredibly annoying.
View ArticleComment by harry
@stezz Thanks for the insight. Maybe you could allow a small number of *real* tabs as soon as you have trimmed memory consumption far enough. 2 *real* tabs would already improve my browsing experience...
View ArticleComment by casanunda
@fawz I agree with your need. Have you tried "Webcat" browser from Jolla store? it's at least a native app and can use real tabs as well as landscape view.
View ArticleComment by fawz
To be honest I wouldn't mind the performance hit. Sometimes I desperately need this functionality, being able to turn it on with a hidden setting would be worth a lot. At this point I need to use...
View ArticleComment by javispedro
Gecko for Firefox "compresses" inactive tabs. Not sure how easily can that be done on lite embed. Also, please provide the option to force-enable keeping tabs loaded. Personally I have plenty of free...
View ArticleComment by Venemo
@veskuh Ah, I see! So the trouble is not Gecko itself but the Jolla adaptation of it.
View ArticleComment by veskuh
@venemo It's not as simple as that. Gecko needs to be adapted to OS for things like input, dialogs, video, 3D, etc. Our adaptation still has some legacy code that takes memory, and our configuration...
View ArticleComment by Aigner
@veskuh: Even if khtml is deprecated and Qt is switching to Blink, QtWebView API won't change dramatically... The "Tiny Web Browser" by Mike7b4 proves that a Qt-Browser runs fine on Sailfish - It even...
View ArticleComment by Venemo
@stezz Sorry, I don't get it. Gecko obviously runs quite fine on lower spec hardware, I don't see what more optimalizations you need.
View ArticleComment by stezz
@Venemo I said that we did not have time to optimize memory consumption on our build of Gecko I did not say it was impossible nor we will never do it. With your argument you just proved that it is...
View ArticleComment by Venemo
@qwazix @stezz The Firefox OS device with 256MB RAM also supports multiple real tabs just fine. Note: I think Firefox OS unloads tabs in the background in out-of-memory scenarios.
View ArticleComment by qwazix
not to mention that it completely contradicts "true multitasking" also the N900 with 256mb of ram handles multiple gecko windows just fine
View ArticleComment by Venemo
@stezz So please fix this - it makes using the browser on the Jolla a huge displeasure.
View Article
