W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2013

Re: [whatwg] Page reflow when entering/exiting fullscreen

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 23 Jul 2013 10:48:31 -0700
Message-ID: <CADnb78iSmOCNeh2Q3NowxqHDXk5SYrkZcnbCis=KKztjFPPPEw@mail.gmail.com>
To: Matt Falkenhagen <falken@chromium.org>
Cc: WHATWG <whatwg@whatwg.org>
On Mon, Jul 22, 2013 at 6:58 PM, Matt Falkenhagen <falken@chromium.org> wrote:
> When an element goes fullscreen, should the browser try to retain the
> layout of the underlying document, e.g., by creating a placeholder for
> the element?

It's not entirely clear to me what you mean by placeholder.


> With the top layer, it's possible to style the fullscreened element and
> ::backdrop such that the underlying document is visible. In such a case,
> it may be surprising for the user to see the layout change. The scroll
> position may also change.
>
> As far as I can tell, the Fullscreen spec doesn't say anything normative
> about retaining the layout. I'm wondering whether it was a deliberate
> decision to leave it up to the author to create a placeholder if
> desired. (As an implementer, this would be easier for me.)

I had not entirely considered scroll position. I sort of assumed that
would not change, but maybe that's not the best behavior. I don't
really have strong opinions here.


> WebKit and Blink actually already use a placeholder to prevent the page
> from reflowing when entering/exiting fullscreen, but there are some
> limitations. For example, inline elements don't get placeholders.



--
http://annevankesteren.nl/
Received on Tuesday, 23 July 2013 17:49:01 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:03 UTC