← back to v136 · explicit-compile-hints-with-magic-comments
conformance · v136
v136 · explicit-compile-hints-with-magic-comments — conformance probe
5 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
magic-comment-does-not-break-parse |
A `//# allFunctionsCalledOnLoad` magic comment is a legal JS comment — adding it must not change script semantics. spec ↗ | script | … | |
magic-comment-allowed-at-eof |
A trailing magic-comment hint near end-of-file remains a legal comment. spec ↗ | script | … | |
function-prototype-still-callable |
Function.prototype.call/apply still work on hinted functions — the hint is informational, not a behavioural change. | script | … | |
script-tag-supports-eager-parse |
A <script> tag created in JS can carry the hint comment in its source without throwing on insertion. | script | … | |
module-script-tolerates-comment |
A module script tolerates the magic comment without affecting export semantics (tested via dynamic import of a data URL). | script | … |