W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

[Bug 28614] New: Weaken the requirement of the time of running async steps

From: <bugzilla@jessica.w3.org>
Date: Wed, 06 May 2015 04:39:48 +0000
To: public-webapps@w3.org
Message-ID: <bug-28614-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28614

            Bug ID: 28614
           Summary: Weaken the requirement of the time of running async
                    steps
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Fullscreen
          Assignee: annevk@annevk.nl
          Reporter: quanxunzhen@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

For requestFullscreen() and exitFullscreen(), the current spec requires UAs to
execute the async steps "as part of the next animation frame task".

I propose that UAs should be allowed to decide when to run those steps, instead
of being forced to run them in the next animation frame.

This change would allow UA to have some transition before putting the page into
fullscreen state (e.g. fade the screen to black)

In addition, UAs may need to do some extra work to put its window into
fullscreen (which could be async because of API of OS), hence at exactly the
next frame, it is possible that the window hasn't been in fullscreen yet, which
means a page may need to rely on the following resize event to correct some
dimensions it uses instead of only the fullscreenchange event.

It seems that, what is "the next animation frame task" has no definition yet.
With this change, we will not need to define that anymore.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 6 May 2015 04:39:50 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC