Diagnostic boundaryA Chrome success plus a Firefox blank surface points first to client bootstrap, cached assets, or a browser API boundary—not automatically to provider credentials or Session corruption.

Classify the failure

Chrome works

Server, profile, and Session data are probably reachable.

Firefox blank

Capture the first Console and Network evidence.

Both fail

Move to server, profile, provider, or persistence checks.

Preserve evidence before repair

  1. Open Firefox Developer Tools and preserve Console logs.
  2. Reload once; record the first exception, not the cascade.
  3. Persist Network logs and inspect fetch, WebSocket, 4xx, and 5xx requests.
  4. Compare document, chunk, stylesheet, origin, and port with Chrome.
  5. Retry in a private window or clean profile with extensions disabled.
  6. Only then investigate server boundaries; do not delete the Session directory.
Report the smallest reproducible trace.

Include exact DSH and Firefox versions, origin, profile, first exception, failed request, and the Chrome comparison. Redact tokens, cookies, paths, and Session contents.

Read the complete runbook.

The canonical guide explains the browser, service-worker, WebSocket, and upstream-reporting boundaries.

Read the full guideStar on GitHub