| browser.js |
|
0 |
| escaped-bang-041.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \041
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
456 |
| escaped-bang-u21.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \u{21}
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
460 |
| escaped-bang-u0021.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \u0021
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
460 |
| escaped-bang-x21.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \x21
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
456 |
| escaped-hash-043.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \043
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
456 |
| escaped-hash-u23.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \u{23}
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
460 |
| escaped-hash-u0023.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \u0023
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
460 |
| escaped-hash-x23.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters \x23
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
456 |
| escaped-hashbang.js |
---
esid: pending
description: >
Hashbang comments should not be allowed to have encoded characters
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
458 |
| eval-indirect.js |
---
esid: pending
description: >
Hashbang comments should be available in Script evaluator contexts. (indirect eval)
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
features: [hashbang]
--- |
504 |
| eval.js |
---
esid: pending
description: >
Hashbang comments should be available in Script evaluator contexts. (direct eval)
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
features: [hashbang]
--- |
487 |
| function-body.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at the start of source texts and should not be allowed within function bodies.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
496 |
| function-constructor.js |
---
esid: pending
description: >
Hashbang comments should not be allowed in function evaluator contexts.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
features: [hashbang]
--- |
981 |
| line-terminator-carriage-return.js |
---
esid: pending
description: >
Hashbang comments are terminated by the first LineTerminator: Carriage Return
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
SingleLineCommentChars::
SingleLineCommentChar SingleLineCommentChars[opt]
SingleLineCommentChar::
SourceCharacter but not LineTerminator
LineTerminator::
<LF>
<CR>
<LS>
<PS>
flags: [raw]
features: [hashbang]
--- |
659 |
| line-terminator-line-separator.js |
---
esid: pending
description: >
Hashbang comments are terminated by the first LineTerminator: Line Separator
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
SingleLineCommentChars::
SingleLineCommentChar SingleLineCommentChars[opt]
SingleLineCommentChar::
SourceCharacter but not LineTerminator
LineTerminator::
<LF>
<CR>
<LS>
<PS>
flags: [raw]
features: [hashbang]
--- |
659 |
| line-terminator-paragraph-separator.js |
---
esid: pending
description: >
Hashbang comments are terminated by the first LineTerminator: Paragraph Separator
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
SingleLineCommentChars::
SingleLineCommentChar SingleLineCommentChars[opt]
SingleLineCommentChar::
SourceCharacter but not LineTerminator
LineTerminator::
<LF>
<CR>
<LS>
<PS>
flags: [raw]
features: [hashbang]
--- |
669 |
| module.js |
---
esid: pending
description: >
Hashbang comments should be allowed in Modules.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [module, raw]
features: [hashbang]
--- |
355 |
| multi-line-comment.js |
throw "Test262: This statement should not be evaluated.";
these characters should not be considered within a comment
|
504 |
| no-line-separator.js |
---
esid: pending
description: >
Hashbang comments should not require a newline afterwards
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
features: [hashbang]
--- |
382 |
| not-empty.js |
---
esid: pending
description: >
Hashbang comments should be allowed in Scripts and should not be required to be empty.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
features: [hashbang]
--- |
434 |
| preceding-directive-prologue-sc.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at start of source texts and should not be preceded by DirectivePrologues.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
511 |
| preceding-directive-prologue.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at start of source texts and should not be preceded by DirectivePrologues.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
510 |
| preceding-empty-statement.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at the start of source texts and should not be preceded by empty statements.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
500 |
| preceding-hashbang.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at the start of source texts and should not be preceded by Hashbang comments.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
503 |
| preceding-line-comment.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at the start of source texts and should not be preceded by line comments.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
499 |
| preceding-multi-line-comment.js |
|
507 |
| preceding-whitespace.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at the start of source texts and should not be preceded by whitespace.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
494 |
| shell.js |
|
0 |
| statement-block.js |
---
esid: pending
description: >
Hashbang comments should only be allowed at the start of source texts and should not be allowed within blocks.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
negative:
phase: parse
type: SyntaxError
features: [hashbang]
--- |
476 |
| use-strict.js |
---
esid: pending
description: >
Hashbang comments should not be interpreted and should not generate DirectivePrologues.
info: |
HashbangComment::
#! SingleLineCommentChars[opt]
flags: [raw]
features: [hashbang]
--- |
413 |