On Mon, Feb 23, 2015 at 4:26 PM, Jonas Sicking <jo...@sicking.cc> wrote: > On Mon, Feb 23, 2015 at 4:01 PM, Robert O'Callahan <rob...@ocallahan.org> > wrote: >> On Tue, Feb 24, 2015 at 12:09 PM, Jonas Sicking <jo...@sicking.cc> wrote: >>> >>> I think this would fall over more often than not. >>> >>> Most developers will not write their code to be resilient in the face >>> of being suspended for extended periods of time. Upon reopening they >>> would likely display error dialogs, or updated version of whatever was >>> saved. >>> >>> In fact, I would argue that it's directly harmful to keep even some of >>> the app logic working. It could cause things like overwriting server >>> state with whatever state was serialized into the saved copy. >> >> You missed the part about the jail. > > Sure, the jail would prevent server overwrites. > > But there's still problems like code behaving strange due to being > suspended so long, for example by removing content from the screen > that is "out of date". > > Additionally the jail is more likely to cause error dialogs to appear > due to failed network requests. > > I would also argue that keeping a lot of the page "working" by running > scripts, is going to be even more confusing when that page is then > unable to actually save anything due to the jail. Rather than nuking > all the scripts and ensuring that the only thing the user can do is > scroll around on the page.
Having thought about this overnight... Ultimately I don't feel like I'm convincing anyone on this thread. And I definitely think this is the layout team's call and not mine. I think we're making a different judgement call about how good your average websites will be to use features like ServiceWorkers to cache content for offline usage, and cache the content that users actually want to be available. (I don't for example think that native apps are particularly good at this). And/or we're making different judgement calls about how important it is for users to have content available offline. I would be interested to hear what features that we are getting in return though. I.e. what features we gain by enabling the UIWorker to access the world outside of the DOM. Maybe those features are clearly more valuable than browser-provided offline capabilities and printing. Either way though, I am sad that in our pursuit of competing with native, it feels like we're giving up more and more of the advantages that we do have over native. / Jonas _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
