W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2014

[Bug 26440] New: Allow fullscreenchange events to be synchronized with animation frames

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 Jul 2014 09:06:04 +0000
To: public-webapps@w3.org
Message-ID: <bug-26440-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26440

            Bug ID: 26440
           Summary: Allow fullscreenchange events to be synchronized with
                    animation frames
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Fullscreen
          Assignee: annevk@annevk.nl
          Reporter: philipj@opera.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

http://fullscreen.spec.whatwg.org/#go-fullscreen

Tasks are queued to resize the viewport and fire the fullscreenchange event.

I would like to synchronize changes to the fullscreen element stack and the
events with animation frames, so that any scripts will always see a perfectly
consistent state. I wrote about this and other messy things on blink-dev
recently:
https://groups.google.com/a/chromium.org/d/msg/blink-dev/GLl6aWs9-EM/6Z0IkWgmWJsJ

Unfortunately, the way the spec is phrased doesn't seem to allow for this. I
propose that instead of using the user interaction task source, any script
visible changes and events are tied into the requestAnimationFrame() machinery.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 28 July 2014 09:06:05 UTC

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