Hi Abdoulaye, were you still working on this?

Hi Mike. Yes, I am.

e10s scenario:

1. A DOM element request fullscreen mode.
2. The request is redirected to the parent.
3. Parent enters fullscreen.
4. Parent notifies child that it has finished entering fullscreen.
5. Child goes fullscreen.
6. Then, child notifies parent that it has finished transitioning to fullscreen.
7. Finally, parent notifies observers that fullscreen paint has finished.

Let's go into the details of how step 5 works in the above scenario.
5.a The element that made the request is set to fullscreen.
5.b Then, the document where that element lives is set to fullscreen as well as all of its ancestors until we reach the top-level document. (see Document::ApplyFulscreen method)

Now in Fission world, we may have a request coming from an oop iframe. And it that case since we won't be able to directly access to ancestor documents living in different content processes anymore, we will first notify those content processes (one after the other from bottom to top) to go fullscreen. Once they all do, the content process where the request originated from will be told to enter fullscreen. And then the process continues to step 6...

Dao and smaug, please review the patches.

No need to needinfo when the patch is in review queue.

Hey Abdoulaye - I notice you've got prior approval on the reviews for Part 1, and just got approval on Part 2 yesterday. Is this pretty close to being landable?

Yes it is, I am just waiting for dao approval here.

Are these patches ready to land?

I conferred with Abdoulaye outside of Bugzilla - it sounds like he's sorted things out with Dao in Phabricator, and try looks okay (https://treeherder.mozilla.org/#/jobs?repo=try&revision=18dd6d6f49252a373d35cb12f7d53e86d102a540), so going to try to land these now.

https://hg.mozilla.org/mozilla-central/rev/8b47aa47a640
https://hg.mozilla.org/mozilla-central/rev/fcaa0242c204