26602 2014-08-18 22:20:26 +0000 Cross-process damage control in requestFullscreen() and exitFullscreen()? 2014-08-26 13:16:16 +0000 1 1 1 Unclassified WebAppsWG Fullscreen unspecified PC All RESOLVED INVALID P2 normal --- 1 philipj annevk mike public-webapps public-webapps-bugzilla oldest_to_newest 110269 0 philipj 2014-08-18 22:20:26 +0000 Here's an idea that doesn't fix any bug but may be worthwhile. In requestFullscreen(), wait with the first ready check until just before the resize, so that if it requires IPC, that won't have to be done synchronously before requestFullscreen() returns. "Fullscreen is not supported" could be moved as well, just in case establishing that actually requires inspecting each document. Together with bug 26601 that should leave nothing fancy in the synchronous section. In exitFullscreen(), return immediately after step 1 or 2, or otherwise move the population of parentDocs to the async section. WDYT? 110400 1 philipj 2014-08-21 11:48:18 +0000 On the other hand, this change would require specifying in greater detail when exactly the async steps are run, so that it's well defined which scripts and event handlers run between the requestFullscreen() call and the first async steps. That might not be an improvement. 110588 2 annevk 2014-08-26 09:21:32 +0000 Not sure what to do here. Did you experiment with this? 110604 3 philipj 2014-08-26 13:16:16 +0000 I didn't experiment, unfortunately I'm just speculating on what might be a problem. Doing the cross-process checks synchronously in requestFullscreen() could turn out to be a mistake, but the check needs to be done before the actual resize at a well-defined point for interop, so I don't know how to improve it. Resolving as invalid until the problem turns out to be real.