Sample
Initialize Happy DOM with options and populate markup via document.write or window.DOMParser rather than passing HTML strings to new Window or invoking standalone DOMParser
sha256:53aeae586fae7f02414a22588d189556a779055a4c627064ec6114aee07367ef
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Initialize Happy DOM with options and populate markup via document.write or window.DOMParser rather than passing HTML strings to new Window or invoking standalone DOMParser HOW
- Packages
- happy-dom 20.11.2
- Environment
- node
- Created
- 2026-08-16T16:45:38Z
Commonly assumed
Passing an HTML string to new Window(html) initializes the document markup, or instantiating new DOMParser() parses HTML strings into a DOM tree.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- new Window(html) ignores string arguments because the constructor expects an options object, leaving document.body.innerHTML empty and getElementById returning null.
- new DOMParser() imported standalone from happy-dom throws TypeError on parseFromString due to missing Window context binding.
- window.document.write(html) on an existing Window instance parses the HTML string into the active document.
- new window.DOMParser() bound to a Window instance successfully parses HTML into a new HTMLDocument.
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9