[Bug 26366] It's possible to go fullscreen with an element not in the document from bugzilla@jessica.w3.org on 2014-07-28 (public-webapps-bugzilla@w3.org from July 2014)

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 Jul 2014 13:08:17 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-26366-2532-ve7c8osz9d@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26366

--- Comment #6 from Anne <annevk@annevk.nl> ---
requestFullscreen()
- sets pending element
- queues a task to run these steps
  1) if pending element is unset, return
  2) push pending element to stack
  3) unset pending element
  4) animate (async?)

exitFullscreen()
- queues a task to run these steps
  1) if pending element is set, unset it and return
  2) pop stack
  3) animate (async?)

Since they're separate tasks, there should be no problem, right? They can
happen quite shortly after each other. Making that animate smoothly would be up
to the implementation.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 28 July 2014 13:08:18 UTC