Limited availability
Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.
The currententrychange event of the Navigation interface is fired when the Navigation.currentEntry has changed.
This event will fire for:
Same-document navigations (e.g., back() or traverseTo()).
Replacements (i.e., a navigate() call with history set to replace).
Other calls that change the entry's state (e.g., updateCurrentEntry(), or the History API's History.replaceState()).
This event fires after the navigation is committed, meaning that the visible URL has changed and the NavigationHistoryEntry update has occurred. It is useful for migrating from usage of older API features like the hashchange or popstate events.
Use the event name in methods like addEventListener(), or set an event handler property.
addEventListener("currententrychange", (event) => { })
oncurrententrychange = (event) => { }
Navigation data reporting:
navigation.addEventListener("currententrychange", () => {
const data = navigation.currentEntry.getState();
submitAnalyticsData(data.analytics);
});
Setting up a per-entry event:
navigation.addEventListener("currententrychange", () => {
navigation.currentEntry.addEventListener("dispose", genericDisposeHandler);
});
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4