Hi, I am not sure how does this matter if setVisible is too late or too early while an app is launching. The fact is while we launch an app, the previous app is still foreground after it's going out of viewport && the foreground app is loaded.
We were facing some critical cases as an app is killed while it's still launching before, See https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/app_window_manager.js#L151 For the question here couldn't we just set docShell.isActive = true by default? What will happen if the setVisible call is too late and what state if no one calls setVisible on the iframe? Neither foreground nor background? -Alive Gabriele Svelto <[email protected]> 於 2014/4/26 下午3:15 寫道： > On 26/04/2014 01:48, Jonas Sicking wrote: >> That only works once an app is far enough along in the launch process >> that it's able to run javascript. We need to give apps a high priority >> before then. >> >> Is gaia currently setting the "visibility flag" on <iframes> of >> launching apps right away? If not, we should make that happen. > > We should but I still wanted to measure how long it takes for the whole > process to happen. I just haven't got enough time to do it yet (still > too busy fixing v1.3t bugs). > > Gabriele > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g -- Alive C. Kuo, Senior Front-end/Software Engineer, FirefoxOS, MoCo. Taiwan, Taipei office. [email protected]
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
