Potential error in connection between "Document destroy" and "Document abort" algorithms #9148
Description
Seems like there is an issue in https://html.spec.whatwg.org/multipage/document-lifecycle.html#destroy-a-document that "document destroy" algorithm can call "document abort" on navigables with already nulled active documents of descendant navigables:
- Destroy the active documents of each of document's descendant navigables.
after recursive destroy on step 1 all descendant navigables will have document=null in active session history because of step 7:
- Set document's node navigable's active session history entry's document state's document to null.
and then on step four of initial destroy call
- Abort document.
abort will fail to access active document for a child navigable here because it was nulled before on step 7 in destroy steps:
- Abort the active documents of each of document's descendant navigables
Questions:
Is null check for active document assumed here? If so maybe it worth to mention null check explicitly.
if this supposed to work without null check on active document then there might be param whether abort should go recursively.