THE GITHTML FIELD GUIDE
Diagnose a blank HTML page when JavaScript is off
Inspect whether the HTML body contains the document text or only an empty application container. If the content is created by JavaScript, request or generate a static export that includes it. Keep scripts off while diagnosing unfamiliar files; a blank page alone is not evidence that enabling them is necessary or safe.
Identify the kind of file
Many web applications deliver a small HTML shell and construct the interface after scripts load. A file named report.html can therefore contain almost no report content. Look for an empty root element, script bundle references, and the absence of recognizable headings or paragraphs. Compare that with a static document whose text is present directly in the source.
A second possibility is that real content exists but CSS hides it until a script adds a class. Search for rules involving display, visibility, opacity, or loading states. This distinction matters: an application shell needs an authoring or export change, while hidden static content may need a simpler presentation fix. Do not assume every blank page has the same cause.
Recover content at the authoring stage
Ask the author for a static reading artifact generated from the same source. The export should include the report's actual values and explanations, not just a screenshot of the application or another shell that still fetches its data. A good handoff identifies the data date and any features intentionally omitted from the static version.
If you control the source, make the core content visible by default and treat interactive enhancements as optional. A chart can have a static summary and data table even when an interactive view exists elsewhere. A useful fallback is specific enough to answer the reader's question; a message saying Enable JavaScript is merely a description of the dependency.
Use a safe diagnostic sequence
gitHtml leaves JavaScript off by default. Preserve that baseline for unfamiliar documents. If a trusted document genuinely requires interaction, assess the source and resources separately before changing settings. A script can initiate network activity or alter the displayed content, so a settings change should be deliberate and limited to a understood need.
- Check whether the expected title or a distinctive sentence appears in the HTML source.
- Inspect empty mount containers and external script references.
- Ask whether a static export is available from the authoring tool.
- Confirm that CSS is not hiding otherwise complete content.
- Reopen the corrected artifact with JavaScript still off and check the actual answer, not just whether the page is no longer blank.
Sources and further reading
AI-assisted writing with source-linked guidance and illustrative examples. Read our editorial approach or report a correction.