### What is the issue with the HTML Standard? I encountered this investigating why Gecko crashes in [navigate-multiple-navigation-navigate.html](navigation-api/navigate-event/navigate-multiple-navigation-navigate.html). Gecko implements [this assert](https://html.spec.whatwg.org/#maybe-set-the-upcoming-non-traverse-api-method-tracker:~:text=Assert%3A%20navigation%27s%20upcoming%20non%2Dtraverse%20API%20method%20tracker%20is%20null) as assert in the code, which gets hit when [navigate `#3`](https://github.com/web-platform-tests/wpt/blob/master/navigation-api/navigate-event/navigate-multiple-navigation-navigate.html#L25) gets called. As I understand, the assert is hit because the navigate to `#2` [aborts all ongoing navigations](https://html.spec.whatwg.org/#navigate-event-firing:promote-an-upcoming-api-method-tracker-to-ongoing:~:text=Abort%20the%20ongoing%20navigation%20given%20navigation%2E,-If), which aborts navigate `#1`, which then synchronously runs navigate to `#3`, which [maybe creates a new upcoming API tracker](https://html.spec.whatwg.org/#dom-navigation-navigate:~:text=Let%20apiMethodTracker%20be%20the%20result%20of%20maybe%20setting%20the%20upcoming%20non%2Dtraverse%20API%20method%20tracker%20for%20this%20given%20info%20and%20serializedState%2E), which asserts because there already exists one (the one for the navigate to `#2`). This all happens _before_ [promoting the upcoming API tracker to ongoing](https://html.spec.whatwg.org/#inner-navigate-event-firing-algorithm:~:text=Promote%20an%20upcoming%20API%20method%20tracker%20to%20ongoing%20given%20navigation%20and%20destinationKey%2E) in the inner navigate event firing algorithm. cc @noamr @zcorpan @farre