[Bug 27865] Merge fullscreen element stack into top layer

https://www.w3.org/Bugs/Public/show_bug.cgi?id=27865

--- Comment #8 from Xidorn Quan <quanxunzhen@gmail.com> ---
(In reply to Philip Jägenstedt from comment #7)
> As for requests in iframes, is this really different from a non-iframes
> case? As long as the iframe element itself can be put into the top layer,
> which it presumably can, then wouldn't it work out?

It is really different. The problem is, we cannot move an element inside the
iframe to the top of the stack without also puting the whole iframe there.

For example:

+-iframe
| |
| +-div id=a
|   |
|   +-div id=b
|
+-div id=c

Then we call:
1. request fullscreen on #a, then
2. request fullscreen on #c, then
3. request fullscreen on #b

What should happen? (It doesn't have anything weird with the current check
algorithm, though, but what if it is relaxed to allow such calls?)

The other difference is that we need to dispatch events to subdocuments when we
exit fullscreen from the top. If we have a fullscreen document tree, we will
also need to specify the order of events to dispatch. Which is doable, but just
much more complicated than it currently is.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 2 July 2015 12:48:57 UTC