26677 2014-08-26 21:54:35 +0000 Clarify when :fullscreen applies 2015-07-15 12:53:06 +0000 1 1 1 Unclassified WebAppsWG Fullscreen unspecified PC All RESOLVED FIXED P2 normal --- 1 philipj annevk mike public-webapps public-webapps-bugzilla oldest_to_newest 110647 0 philipj 2014-08-26 21:54:35 +0000 http://fullscreen.spec.whatwg.org/#:fullscreen-pseudo-class If an element at the top of its node document's fullscreen element stack is moved to another document, does the :fullscreen pseudo-class still apply until the old document's fullscreen element stack is updated in exitFullscreen()? If yes, it becomes a bit harder to implement :fullscreen, one would have to have a flag per element instead of checking the the element's node document's fullscreen element stack. Do not like. If no, scripts will immediately observe the change in element.matches(':fullscreen') but the change in oldDocument.fullscreenElement will be async. That's a bit weird, but maybe OK. 111127 1 annevk 2014-09-06 15:28:01 +0000 Why would the change to oldDocument.fullscreenElement be asynchronous? As far as I can tell it is identical to :fullscreen. 111133 2 philipj 2014-09-06 21:44:10 +0000 It's the difference between an element being at the top of any document's fullscreen element stack, and being at the top of that element's node document's fullscreen element stack. The latter makes more sense I think. 111136 3 annevk 2014-09-07 07:05:01 +0000 Oh I see. The removing steps are sometimes synchronous and sometimes not. As per that other bug. This sucks. 122059 4 philipj 2015-07-15 12:53:06 +0000 The spec now says what I asked for: "The :fullscreen pseudo-class must match any element that is that element's node document's fullscreen element."