DioxusLabs/dioxus · error
`GoForwardButton` must have access to a parent router
Error message
`GoForwardButton` must have access to a parent router
What it means
GoForwardButton called use_router_internal() and received None because it was rendered outside a Router subtree. Without router context the button cannot navigate; debug builds panic and release builds render it inactive.
Source
Thrown at packages/router/src/components/history_buttons.rs:144
/// # let mut vdom = VirtualDom::new(App);
/// # vdom.rebuild_in_place();
/// # assert_eq!(
/// # dioxus_ssr::render(&vdom),
/// # r#"<button disabled="true">go forward</button>"#
/// # );
/// ```
pub fn GoForwardButton(props: HistoryButtonProps) -> Element {
let HistoryButtonProps { children } = props;
// hook up to router
let router = match use_router_internal() {
Some(r) => r,
#[allow(unreachable_code)]
None => {
let msg = "`GoForwardButton` must have access to a parent router";
error!("{msg}, will be inactive");
#[cfg(debug_assertions)]
panic!("{}", msg);
return VNode::empty();
}
};
let disabled = !router.can_go_forward();
rsx! {
button {
disabled: "{disabled}",
onclick: move |evt| {
evt.prevent_default();
router.go_forward()
},
{children}
}
}
}
View on GitHub (pinned to 24f6a829df)
Solutions
- Render GoForwardButton inside a Router component so it can access the router context.
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at packages/router/src/components/history_buttons.rs:144 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of DioxusLabs/dioxus@24f6a829df (2026-08-23).
Data as JSON: /api/errors/05069192ca852d25.
Report an issue: GitHub.