Is cancelFullScreen() synchronous or should it queue a task? If you invoke
cancelFullScreen() on a Document of a parent or child browsing context
from the browsing context in whose Document requestFullScreen() was
invoked it should presumably still work, no?
Presumably also if the Document has been navigated away from. In what
scenarios does the "for example the UA might require that only a Document
that last triggered full-screen can cancel it" provision apply?
It is really quite confusing in the draft what "full screen" is associated
with. A Document, a top-level browsing context, the user agent?
--
Anne van Kesteren
http://annevankesteren.nl/
