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

[Bug 26626] New: Populate the full list of event targets before firing any events

From: <bugzilla@jessica.w3.org>
Date: Thu, 21 Aug 2014 09:01:11 +0000
To: public-webapps@w3.org
Message-ID: <bug-26626-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26626

            Bug ID: 26626
           Summary: Populate the full list of event targets before firing
                    any events
           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/#dom-document-exitfullscreen

9.6. If exitDocs's last document has a browsing context container, let topDoc
be that browsing context container's node document, and then remove the top
element from topDoc's fullscreen element stack and fire an event named
fullscreenchange on topDoc.

The event handlers already fired in these steps can have moved the iframe
element of exitDocs's last document, so that the fullscreenchange event ends up
firing on a document other than the document that the iframe went fullscreen
in.

It looks like moving part of step 9.6 to 9.3 and letting step 9.5 fire all of
the events should fix this.

It would also be nice if step 9.4 were also more explicit about first creating
a list of documents and then firing events.

For requestFullscreen(), bug 26601 should solve the problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 21 August 2014 09:01:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:26 UTC