Feature Test Links Link to heading

Every row below is rendered directly from app/linkrouter-rules-examples.json — the same fixtures the unit-test suite consumes — so the page is a 1:1 map of what the router should do: Input (what you open) → Expected Output (what the target browser should show).

Setup — enable the relevant feature before testing it:

• Shortener hosts and Host rewrites ship disabled (opt-in) — flip the specific host ON in Settings first.
• Rules and Redirect formats must exist (add them, or keep) in Settings.
• Query-param filters ship enabled by default.

See How to test for a reliable workflow.

How to test Link to heading

The links below exercise LinkRouter end-to-end. Because LinkRouter is your default browser, a bare in-browser tap goes straight through it, which is exactly what we want to observe — but it leaves nothing to compare against the Expected Output shown in this page. The reliable workflow:

1. Open the link in an app that doesn’t handle browsing itself (a messaging app’s share target, a notes / todo app, or a PDF). That way you watch the dispatch in real time and the target browser’s result appears alongside this page.
2. Print this page to a PDF, or just use your browser’s own Ctrl/Cmd+Print. Then read it on the phone and tap the links straight from the document.

Print to PDF

3. Open the Input link and confirm the target browser opened exactly the Expected Output shown in the adjacent cell.

Rules

AMP cache unwrap

Redirect formats

Query-param filters

Shortener hosts

Host rewrites