[Webkit-unassigned] [Bug 84796] Implement the new stacking layer needed by the Fullscreen API and the new <dialog> element
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Sep 13 03:45:52 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=84796
Matt Falkenhagen <falken at chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jer.noble at apple.com
--- Comment #3 from Matt Falkenhagen <falken at chromium.org> 2012-09-13 03:46:18 PST ---
It seems that RenderFullScreen works now by wrapping a renderer when its element becomes full screen and then unwrapping when it's no longer full screen. So there is one element (and its subtree) that is full screen at a time.
I wonder if we can do something like this instead:
- RenderFullScreen (perhaps renamed "RenderTopLayer") is a child of RenderView
- When an element is added to the top layer, its renderer becomes a child of RenderFullScreen
- When an element is removed from the top layer, its renderer is returned to its original place
- RenderFullScreen handles the special layout and stacking of the elements as described in the spec (z-index has no effect, position:"static" computes to "absolute", and the static position for top, left, right are zero).
Does that sound like an okay approach? Maybe dynamic changes to the DOM tree would be problematic for returning no longer fullscreened elements to their original place in the render tree.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list