This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
As specified, the stack is first popped, which will be visible to scripts (fullscreenElement) and CSS (:fullscreen). The resizing and event firing is done in a later task, so scripts will be able to observe the inconsistent state. In short, it should mirror the "go fullscreen" algorithm, which doesn't have the problem.
https://github.com/whatwg/fullscreen/commit/6bc47c40c2d84938b4a9ea69a3c46800fc2dabe3
Thanks!