document.location.href should be updated before intercept handler is run.

[LEW21]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure it has not already been reported

Version (i.e. v2.x.x)

1.0.1-alpha.209

Node.js version (i.e. 18.x, or N/A)

No response

Operating system

None

Operating system version (i.e. 20.04, 11.3, 10, or N/A)

No response

Description

As per MDN ("The URL has already changed"), the page URL should be already changed when the interception handler is called.

Steps to Reproduce

window.navigation.addEventListener('navigate', ev => {
	ev.intercept({
		async handler() {
			console.log(document.location.pathname)
		}
	})
})

window.navigation.navigate('/xyz')

Expected Behavior

In Chrome, this logs '/xyz'. With the polyfill, it logs whatever the pathname was before.

[fabiancook]

This appears to be because history is updated only on current entry change

navigation/src/get-polyfill.ts

Lines 756 to 779 in 6f66ed2

	navigation.addEventListener("currententrychange", ({ navigationType, from }) => {
	// console.log("<-- currententrychange event listener -->");
	const { currentEntry } = navigation;
	if (!currentEntry) return;
	const { key, url } = currentEntry;
	if (ignoreCurrentEntryChange.delete(key) || !currentEntry?.sameDocument) return;
	const historyState = getNavigationEntryWithMeta(navigation, currentEntry, patchLimit);
	// console.log("currentEntry change", historyState);
	switch (navigationType || "replace") {
	case "push":
	return pushState(historyState, "", url)
	case "replace":
	return replaceState(historyState, "", url)
	case "traverse":
	const delta = currentEntry.index - from.index;
	ignorePopState.add(key);
	return historyGo(delta);
	case "reload":
	// TODO
	}
	});

I'll investigate updating this earlier in the polyfill and then reverting the change if it was aborted.