Can a fully active document have a null browsing context?

[rakuco]

I'm asking this in the context of w3c/screen-wake-lock#362 -- one of the spec's algorithms does something like this:

• Let document be this's relevant global object's associated Document.
• ...
• If document's browsing context is null, return a promise rejected with "NotAllowedError" DOMException.
• If document is not fully active, return a promise rejected with with a "NotAllowedError" DOMException.
• ...

I'd like to remove the browsing context check, as I can't think of a case where the relevant global object's associated Document is fully active and has a null browsing context, but I feel like I should double check first.

[domenic]

This is not possible.

All documents that are even put into session history, are created through algorithms which set their browsing context to a non-null value.

Then, for the case of the browsing context becoming null, that only happens in https://html.spec.whatwg.org/#destroy-a-document , which makes the document non-active in step 7.

Hope this helps!