This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26484 - Order of fullscreenchange events has reversed in requestFullscreen()
Summary: Order of fullscreenchange events has reversed in requestFullscreen()
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Fullscreen (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-31 16:18 UTC by Philip Jägenstedt
Modified: 2014-07-31 21:01 UTC (History)
2 users (show)

See Also:

Attachments

Description Philip Jägenstedt 2014-07-31 16:18:01 UTC 
Previously the documents would notified from the top-level document and down, now it is the other order. The former order was sensible, so change "append" to "prepend" in "While the last element in fullscreenElements is in a nested browsing context, append its browsing context container to fullscreenElements."
Comment 1 Anne 2014-07-31 19:04:46 UTC 
Isn't that preserved by iterating from last to first?

But using prepend is probably clearer.
Comment 3 Philip Jägenstedt 2014-07-31 21:01:21 UTC 
Oh, I missed the "from last to first" bit.