The browser navigation effect: push (or replace) a History entry, then announce it.
The announcement is what closes the loop: the browser adapter listens for
NAVIGATION_EVENT (and popstate), so a navigation re-enters the kernel as a new
incoming event, and the page for the new path is resolved the same way the first one
was. Nothing here is imported by the router's matching code, so a platform that has no
History API simply supplies its own navigator.
The browser navigation effect: push (or replace) a History entry, then announce it.
The announcement is what closes the loop: the browser adapter listens for
NAVIGATION_EVENT(andpopstate), so a navigation re-enters the kernel as a new incoming event, and the page for the new path is resolved the same way the first one was. Nothing here is imported by the router's matching code, so a platform that has no History API simply supplies its own navigator.