I had raised some questions earlier in another thread (Halting/Refreshing Apps on the Phone), one of which was that the commonly supported window.close() method didn't work on Firefox (any version) and the documentation says it won't work (but doesn't say why it doesn't work on Firefox when it works on Chrome and IE). Jonas Sicking thinks window.close() makes sense for a phone, but I'm now not sure, and part of this is that I'm not sure what happens when an app is "open". There's a great little article on having multiple "open" apps at https://support.mozilla.org/en-US/kb/navigate-between-open-applications-firefox-os.
My questions is this: if an app is open (but not in the foreground), is it "running" or "halted"? Does it take up resources? Or like some other phone systems, does it start shutting down older "open" apps when it runs out of memory? What is the application lifecycle about for a Firefox OS app? Anyone know? Any references to this? What does an app do when no one is looking? So my real question is, should we be allowed to quit an app in our code? My idea is to put a button that says "Quit" on one of the main screens. Or is this undesirable or a security risk? -- Bob Thulfram -- http://firefoxosgaming.blogspot.com/ _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
