We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2015-05-29 13:36:39 +0200 |
With or without android support, the native browser is so unreliable that it is nearly useless. If multiple "tabs" (let's admit it, those aren't even tabs) are running, it is not uncommon to see the whole browser being killed if I open some page running heavy javascript scripts. Can we at least make the browser to run in multiple instances like it is on N9, so that if the process killer kicks in, it has a higher chances to kill some of the running tabs, but not ALL of them?
Yes, I do realize there are other browsers offering the same behavior, but can we have the native browser that does this also?
2 | retagged |
With or without android support, the native browser is so unreliable that it is nearly useless. If multiple "tabs" (let's admit it, those aren't even tabs) are running, it is not uncommon to see the whole browser being killed if I open some page running heavy javascript scripts. Can we at least make the browser to run in multiple instances like it is on N9, so that if the process killer kicks in, it has a higher chances to kill some of the running tabs, but not ALL of them?
Yes, I do realize there are other browsers offering the same behavior, but can we have the native browser that does this also?