Skip to content

Conversation

@AtkinsSJ
Copy link
Member

See commits for details.

This is used from a few different places in the spec.
I missed where this change happened in the spec. The second half of
abort_the_ongoing_navigation() becomes a separate method, which is
slightly rearranged. I've placed this in Navigation instead of
NavigateEvent because of how many steps poke at the Navigation's
internals.

The text here includes the amendments I made in
whatwg/html#11967 to correct a variable name.

A bonus is that we now actually populate the ErrorEvent instead of
leaving it blank.
Corresponds to:
whatwg/html@93634ae

The current live spec has been rearranged since this went in, so that
these steps are no longer located here. But that's a much larger change
that I don't want to implement right now. See here:
whatwg/html@e09d102

While I was at it, I also made use of extract_error_information() to
populate the ErrorEvent.
@AtkinsSJ AtkinsSJ force-pushed the navigation-spec-changes branch from 0f80d9d to 59a0205 Compare November 27, 2025 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant