files/en-us/web/api/navigationprecommitcontroller/addhandler/index.md
{{APIRef("Navigation API")}}
The addHandler() method of the {{domxref("NavigationPrecommitController")}} interface allows you to dynamically add a handler callback function in precommit code, which will then be run after the navigation has committed.
This is useful when the navigation workflow depends on information that is not know until precommit code has started running.
If the precommit and (post-commit) handler are independent, the handler can be specified in the in the options.handler argument passed to {{domxref("NavigateEvent.intercept()")}}.
addHandler(handler);
handler
: A callback function that defines the post-commit navigation handling behavior should be; it returns a promise.
The handler callback is invoked as though it was passed to the NavigateEvent.intercept() method, and will run after the {{domxref("Navigation.currentEntry", "currentEntry")}} property has been updated.
None (undefined).
InvalidStateError {{domxref("DOMException")}}
SecurityError {{domxref("DOMException")}}
false.For more examples see {{domxref("NavigationPrecommitController")}}.
This example shows a precommitHandler implementation that fetches data for a page and uses addHandler() to add different handlers based on the page type (the implementations of the fetchConfig, setupVideoPlayer() and setupArticleView() are not given).
navigation.addEventListener("navigate", (event) => {
event.intercept({
async precommitHandler(controller) {
const pageData = await fetchConfig();
if (pageData.type === "video") {
controller.addHandler(() => setupVideoPlayer());
} else {
controller.addHandler(() => setupArticleView());
}
},
});
});
{{Specifications}}
{{Compat}}