navigator.install() has three call shapes: the current document, a background document URL, and a background document URL plus an explicit manifest id. Build a call, run the real API when the browser exposes it, and exercise the fallback branches that production install buttons need.
runtime checks
checking
navigator.install
JavaScript is checking API availability.
checking
current document
JavaScript is checking the manifest link.
checking
secure context
JavaScript is checking the page context.
call builder
install target
Used by the one-argument and two-argument signatures. The target document must link to a manifest with an id.
Used by the two-argument signature. The value must match the target manifest's computed id or id member.
live outcome
idle
signatures
0 parameters
current document install
Uses the document already loaded in this tab. It is document-backed: the browser reads this page's linked manifest and installability state.
Requires a user gesture.
Requires a valid linked web app manifest with an id.
Can reject when the page is not installable or the user cancels.
1 parameter
document URL install
Installs a background document by URL. The target document supplies the manifest, so the URL is not just a static manifest fetch.
The install URL must be an HTTP(S) document URL.
The target document must link to a manifest with an id.
Invalid or missing manifests should reject as a data problem.
2 parameters
URL plus manifest id
Installs the target document only if the supplied manifest id matches the computed id after parsing the target manifest.
The install URL still points at a document.
The manifest id disambiguates the app identity.
Mismatched or malformed ids need a clean fallback path.
defensive branches
fallback lab
These buttons route the same generated call through the named production fallback branch. The real run buttons above still call navigator.install when the browser exposes it.