>> While an element is fullscreen, the UA imposes CSS style
>> "position:fixed; left:0; top:0; right:0; bottom:0" on the element and
>> aligns the viewport of its DOM window with the screen. Only the
>> element and its children are rendered, as a single CSS stacking context.
> 
> So this makes it a very element-focused API (as does the
> enterFullscreen() method on Element that you propose above).
> 
> Another approach would be to leave it entirely up to the page author to
> style their page differently when in fullscreen, and not have the API
> force them to focus on one element. Then the API would probably be on
> the Window object, and the UA would simply transition the view to a
> fullscreen presentation. There could be a pseudo-class to the body, or a
> way to use media queries to allow the author can apply different styles
> for fullscreen.
> 
> In this scenario the author is not forced to nest all their fullscreen
> content under one element, and can continue to show the rest of the page
> content (maybe dimmed out by a semi-transparent overlay div) in the
> background.

Well, as an author, you can always choose to make the body element go
fullscreen, wouldn't you?

So you can have both:
- use a single div with all it's content
- use a video element
- or use the body, so that the whole page goes fullscreen.

And if there is a pseudo-class on this element, you can always style the
content accordingly.


Best regards,

Frank Hellenkamp

-- 
frank hellenkamp | interface designer
solmsstraße 7 | 10961 berlin

+49.30.49 78 20 70 | tel
+49.173.70 55 781 | mbl
+49.3212.100 35 22 | fax
jo...@depagecms.net

http://www.depagecms.net
http://immerdasgleiche.de
http://everydayisexactlythesame.net/


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to