After bug 1126230, it will be impossible for chrome written in HTML to put anything on top of a document in fullscreen. It would be unfortunate for browser.html and Firefox OS. (XUL browser is fine because it cannot be out-of-flow, and thus cannot be put in the top layer at all.) I guess we have two ways to fix this: 1. add a mechanism to allow putting element on top of the top layer (e.g. adding another CSS property to do so) 2. do not put <iframe mozbrowser> in the top layer when its content enters fullscreen I'm not pretty sure which way is better.
So in bug 1126230, for fixing the failure on a Gij test, we currently take the second way via not setting -moz-top-layer on :-moz-browser-frame. If we decide it is what we want, then we can close this bug. If we still hope to allow putting something on top of the top layer manually, we probably could do that in this bug.
I think we have this mechanism now. With bug 1215360, anonymous content added via Document.InsertAnonymousContent method is rendered on top of the top layer, which can be used for chrome to display things on top of fullscreen content.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Depends on: 1215360
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.