Bug 1620341 Comment 8 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Let me summarize how does it works in this scarino.

In non-e10s case,
[non-e10s-1]   @DOMFullscreenParent.jsm
handleEvent(MozDOMFullscreen:Exited) 
https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenParent.jsm#88
--> call fullScreen.cleanDomFullscreen() 

[non-e10s-2]  @browser-fullScreenAndPointerLock.js 	
cleanupDomFullscreen(aActor)
https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/base/content/browser-fullScreenAndPointerLock.js#490
--> Send "DOMFullscreen:CleanUp" MSG without remoteFrameBC. (https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/base/content/browser-fullScreenAndPointerLock.js#557)
--> At this time, we also restore the chrome UI from fullscreen.

[non-e10s-3]  @DOMFullscreenChild.jsm	 
receiveMessage(DOMFullscreen:CleanUp)
--> No remoteFrameBC. Don't set this. _isNotTheRequestSource (https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenChild.jsm#55)

[non-e10s-4]  @DOMFullscreenChild.jsm	
handleEvent(MozDOMFullscreen:Exited) 
--> Send "DOMFullscreen:Exit" MSG to parent. (https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenChild.jsm#103)

[non-e10s-5]  @DOMFullscreenParent.jsm     
receiveMessage(DOMFullscreen:Exit)
--> call windowUtils.remoteFrameFullscreenReverted()(https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenParent.jsm#44)
Revision 1 by
on 
Let me summarize how does it works in this scarino.

In non-fission case,
[non-fission-1]   @DOMFullscreenParent.jsm
handleEvent(MozDOMFullscreen:Exited) 
https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenParent.jsm#88
--> call fullScreen.cleanDomFullscreen() 

[non-fission-2]  @browser-fullScreenAndPointerLock.js 	
cleanupDomFullscreen(aActor)
https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/base/content/browser-fullScreenAndPointerLock.js#490
--> Send "DOMFullscreen:CleanUp" MSG without remoteFrameBC. (https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/base/content/browser-fullScreenAndPointerLock.js#557)
--> At this time, we also restore the chrome UI from fullscreen.

[non-fission-3]  @DOMFullscreenChild.jsm	 
receiveMessage(DOMFullscreen:CleanUp)
--> No remoteFrameBC. Don't set this. _isNotTheRequestSource (https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenChild.jsm#55)

[non-fission-4]  @DOMFullscreenChild.jsm	
handleEvent(MozDOMFullscreen:Exited) 
--> Send "DOMFullscreen:Exit" MSG to parent. (https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenChild.jsm#103)

[non-fission-5]  @DOMFullscreenParent.jsm     
receiveMessage(DOMFullscreen:Exit)
--> call windowUtils.remoteFrameFullscreenReverted()(https://searchfox.org/mozilla-central/rev/3ce874dc2703831af3e5ef3a1d216ffd08057fa5/browser/actors/DOMFullscreenParent.jsm#44)

Back to Bug 1620341 Comment 8