c***@googlecode.com
2013-07-22 20:42:35 UTC
Comment #6 on issue 240576 by ***@chromium.org: Migrate fullscreen to
use top layer
http://code.google.com/p/chromium/issues/detail?id=240576
The layout behavior of fixed-position elements is very different on mobile.
To make the matter more complicated, the behavior is going to change in
near future (http://goo.gl/aSEyF). It probably doesn't matter anymore
though. After some discussion we decided that it is most sensible to force
page scale factor the lowest possible value when entering fullscreen.
I have a few more question. How flexible is the fullscreen/backdrop pseudo
elements? Can we assign them different CSS positioning? Size that's smaller
than the screen? Opacity? Transparent background? I would imgine that some
people want such flexibity to implement feature like this:
http://lokeshdhakar.com/projects/lightbox2/
There are 2 known difficulties to support fancy backdrops:
1. Android (and possibly Google TV) uses special hardware overlay for
fullscreen video, for performance and DRM reason. We won't be able to
composite such hardware overlay. It has to be on bottom of everything. As
such, we won't be able to support anything that has a z-order lower than
the fullscreen'd video, like backdrop with background image or
transparency. The only backdrop we can do is a fullscreen blackout.
2. Need to implement placeholder for the fullscreen'd element. Otherwise
the document will reflow, which looks bad to the user. Another reason we
want a placeholder (whether to support fancy backdrops or not) is that
reflowing could mess up the scroll position.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
use top layer
http://code.google.com/p/chromium/issues/detail?id=240576
The layout behavior of fixed-position elements is very different on mobile.
To make the matter more complicated, the behavior is going to change in
near future (http://goo.gl/aSEyF). It probably doesn't matter anymore
though. After some discussion we decided that it is most sensible to force
page scale factor the lowest possible value when entering fullscreen.
I have a few more question. How flexible is the fullscreen/backdrop pseudo
elements? Can we assign them different CSS positioning? Size that's smaller
than the screen? Opacity? Transparent background? I would imgine that some
people want such flexibity to implement feature like this:
http://lokeshdhakar.com/projects/lightbox2/
There are 2 known difficulties to support fancy backdrops:
1. Android (and possibly Google TV) uses special hardware overlay for
fullscreen video, for performance and DRM reason. We won't be able to
composite such hardware overlay. It has to be on bottom of everything. As
such, we won't be able to support anything that has a z-order lower than
the fullscreen'd video, like backdrop with background image or
transparency. The only backdrop we can do is a fullscreen blackout.
2. Need to implement placeholder for the fullscreen'd element. Otherwise
the document will reflow, which looks bad to the user. Another reason we
want a placeholder (whether to support fancy backdrops or not) is that
reflowing could mess up the scroll position.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs