Originally, the concept for the ideal flow included the ability to load tabs in the background. While incredibly hard, it's still very valuable if we could pull this off, this would help with a lot of UX issues. Filing to keep track
Hey Jim. With all the work that has going into GeckoService and support push notifications if the app is not running.. I was wondering how far we are from something like launching GeckoService and let it open a tab for the next time we go back to the app? Ideally - if the service/process didn't get killed in the meantime - the tab would wait for us, already loaded and rendered. Is this something that is doable (soon) or is GeckoService not the right choice for that?
Just loading Gecko will save a lot of time when the user switches to Fennec, and it's already doable. We can even start a connection in the background for eventually loading the page. Actually loading a tab and the page though, I think will take some effort. We need to teach Gecko to open a window without an available GeckoView. Front-end will need to remember the tabs it has opened, and restore them when the activity is created. I imagine we can reuse the same code that makes "Don't keep activities" work, but I think the remaining work to be done is still non-trivial.
You need to log in before you can comment on or make changes to this bug.