| after-regular-expression-literal-carriage-return.js |
---
description: U+000D CARRIAGE RETURN <CR> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+000D`
</td>
<td>
CARRIAGE RETURN (CR)
</td>
<td>
<CR>
</td>
</tr>
LineTerminator ::
<LF>
<CR>
<LS>
<PS>
--- |
1721 |
| after-regular-expression-literal-em-quad.js |
---
description: U+2001 EM QUAD (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1819 |
| after-regular-expression-literal-em-space.js |
---
description: U+2003 EM SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1821 |
| after-regular-expression-literal-en-quad.js |
---
description: U+2000 EN QUAD (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1819 |
| after-regular-expression-literal-en-space.js |
---
description: U+2002 EN SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1821 |
| after-regular-expression-literal-figure-space.js |
---
description: U+2007 FIGURE SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1829 |
| after-regular-expression-literal-form-feed.js |
---
description: U+000C FORM FEED <FF> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+000C`
</td>
<td>
FORM FEED (FF)
</td>
<td>
<FF>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1758 |
| after-regular-expression-literal-four-per-em-space.js |
---
description: U+2005 FOUR-PER-EM SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1839 |
| after-regular-expression-literal-hair-space.js |
---
description: U+200A HAIR SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1825 |
| after-regular-expression-literal-ideographic-space.js |
---
description: U+3000 IDEOGRAPHIC SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1839 |
| after-regular-expression-literal-line-feed.js |
---
description: U+000A LINE FEED <LF> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+000A`
</td>
<td>
LINE FEED (LF)
</td>
<td>
<LF>
</td>
</tr>
LineTerminator ::
<LF>
<CR>
<LS>
<PS>
--- |
1703 |
| after-regular-expression-literal-line-separator.js |
---
description: U+2028 LINE SEPARATOR <LS> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+2028`
</td>
<td>
LINE SEPARATOR
</td>
<td>
<LS>
</td>
</tr>
LineTerminator ::
<LF>
<CR>
<LS>
<PS>
--- |
1715 |
| after-regular-expression-literal-medium-mathematical-space.js |
---
description: U+205F MEDIUM MATHEMATICAL SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1855 |
| after-regular-expression-literal-nbsp.js |
---
description: U+00A0 NO-BREAK SPACE <NBSP> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+00A0`
</td>
<td>
NO-BREAK SPACE
</td>
<td>
<NBSP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1763 |
| after-regular-expression-literal-nnbsp.js |
---
description: U+202F NARROW NO-BREAK SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1831 |
| after-regular-expression-literal-ogham-space.js |
---
description: U+1680 OGHAM SPACE MARK (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1832 |
| after-regular-expression-literal-paragraph-separator.js |
---
description: U+2029 PARAGRAPH SEPARATOR <PS> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+2029`
</td>
<td>
PARAGRAPH SEPARATOR
</td>
<td>
<PS>
</td>
</tr>
LineTerminator ::
<LF>
<CR>
<LS>
<PS>
--- |
1730 |
| after-regular-expression-literal-punctuation-space.js |
---
description: U+2008 PUNCTUATION SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1839 |
| after-regular-expression-literal-six-per-em-space.js |
---
description: U+2006 SIX-PER-EM SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1837 |
| after-regular-expression-literal-space.js |
---
description: U+0020 SPACE <SP> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+0020`
</td>
<td>
SPACE
</td>
<td>
<SP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1741 |
| after-regular-expression-literal-tab.js |
---
description: U+0009 CHARACTER TABULATION <TAB> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+0009`
</td>
<td>
CHARACTER TABULATION
</td>
<td>
<TAB>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1771 |
| after-regular-expression-literal-thin-space.js |
---
description: U+2009 THIN SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1825 |
| after-regular-expression-literal-three-per-em-space.js |
---
description: U+2004 THREE-PER-EM SPACE (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
Other category “Zs”
</td>
<td>
Any other Unicode “Space_Separator” code point
</td>
<td>
<USP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1841 |
| after-regular-expression-literal-vertical-tab.js |
---
description: U+000B LINE TABULATION <VT> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+000B`
</td>
<td>
LINE TABULATION
</td>
<td>
<VT>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1768 |
| after-regular-expression-literal-zwnbsp.js |
---
description: U+FEFF ZERO WIDTH NO-BREAK SPACE <ZWNBSP> (after regular expression literal)
esid: sec-lexical-and-regexp-grammars
flags: [generated]
info: |
Input elements other than white space and comments form the terminal symbols
for the syntactic grammar for ECMAScript and are called ECMAScript
<em>tokens</em>. These tokens are the reserved words, identifiers, literals,
and punctuators of the ECMAScript language. Moreover, line terminators,
although not considered to be tokens, also become part of the stream of input
elements and guide the process of automatic semicolon insertion
(<emu-xref href="#sec-automatic-semicolon-insertion"></emu-xref>). Simple
white space and single-line comments are discarded and do not appear in the
stream of input elements for the syntactic grammar. A |MultiLineComment| (that
is, a comment of the form `/*`…`*``/` regardless of whether it spans more
than one line) is likewise simply discarded if it contains no line terminator;
but if a |MultiLineComment| contains one or more line terminators, then it is
replaced by a single line terminator, which becomes part of the stream of
input elements for the syntactic grammar.
<tr>
<td>
`U+FEFF`
</td>
<td>
ZERO WIDTH NO-BREAK SPACE
</td>
<td>
<ZWNBSP>
</td>
</tr>
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
--- |
1792 |
| between-form-feed.js |
---
info: FORM FEED (U+000C) between any two tokens is allowed
es5id: 7.2_A1.3_T2
description: Insert real FORM FEED between tokens of var x=1
--- |
345 |
| between-horizontal-tab.js |
---
info: HORIZONTAL TAB (U+0009) between any two tokens is allowed
es5id: 7.2_A1.1_T2
description: Insert real HORIZONTAL TAB between tokens of var x=1
--- |
356 |
| between-nbsp.js |
---
info: NO-BREAK SPACE (U+00A0) between any two tokens is allowed
es5id: 7.2_A1.5_T2
description: Insert real NO-BREAK SPACE between tokens of var x=1
--- |
358 |
| between-space.js |
---
info: SPACE (U+0020) between any two tokens is allowed
es5id: 7.2_A1.4_T2
description: Insert real SPACE between tokens of var x=1
--- |
337 |
| between-vertical-tab.js |
---
info: VERTICAL TAB (U+000B) between any two tokens is allowed
es5id: 7.2_A1.2_T2
description: Insert real VERTICAL TAB between tokens of var x=1
--- |
351 |
| browser.js |
|
0 |
| comment-multi-form-feed.js |
---
info: Multi line comment can contain FORM FEED (U+000C)
es5id: 7.2_A4.3_T1
description: Use FORM FEED(\u000C)
--- |
572 |
| comment-multi-horizontal-tab.js |
---
info: Multi line comment can contain HORIZONTAL TAB (U+0009)
es5id: 7.2_A4.1_T1
description: Use HORIZONTAL TAB(\u0009)
--- |
582 |
| comment-multi-nbsp.js |
---
info: Multi line comment can contain NO-BREAK SPACE (U+00A0)
es5id: 7.2_A4.5_T1
description: Use NO-BREAK SPACE(\u00A0)
--- |
582 |
| comment-multi-space.js |
---
info: Multi line comment can contain SPACE (U+0020)
es5id: 7.2_A4.4_T1
description: Use SPACE(\u0020)
--- |
564 |
| comment-multi-vertical-tab.js |
---
info: Multi line comment can contain VERTICAL TAB (U+000B)
es5id: 7.2_A4.2_T1
description: Use VERTICAL TAB(\u000B)
--- |
578 |
| comment-single-form-feed.js |
---
info: Single line comment can contain FORM FEED (U+000C)
es5id: 7.2_A3.3_T1
description: Use FORM FEED(\u000C)
--- |
570 |
| comment-single-horizontal-tab.js |
---
info: Single line comment can contain HORIZONTAL TAB (U+0009)
es5id: 7.2_A3.1_T1
description: Use HORIZONTAL TAB(\u0009)
--- |
580 |
| comment-single-nbsp.js |
---
info: Single line comment can contain NO-BREAK SPACE (U+00A0)
es5id: 7.2_A3.5_T1
description: Use NO-BREAK SPACE(\u00A0)
--- |
580 |
| comment-single-space.js |
---
info: Single line comment can contain SPACE (U+0020)
es5id: 7.2_A3.4_T1
description: Use SPACE(\u0020)
--- |
562 |
| comment-single-vertical-tab.js |
---
info: Single line comment can contain VERTICAL TAB (U+000B)
es5id: 7.2_A3.2_T1
description: Use VERTICAL TAB(\u000B)
--- |
576 |
| mongolian-vowel-separator-eval.js |
---
esid: sec-white-space
description: >
Mongolian Vowel Separator is not recognized as white space (eval code).
info: |
11.2 White Space
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
<USP> ::
Other category “Zs” code points
General Category of U+180E is “Cf” (Format).
features: [u180e]
--- |
617 |
| mongolian-vowel-separator.js |
---
esid: sec-white-space
description: >
Mongolian Vowel Separator is not recognized as white space.
info: |
11.2 White Space
WhiteSpace ::
<TAB>
<VT>
<FF>
<SP>
<NBSP>
<ZWNBSP>
<USP>
<USP> ::
Other category “Zs” code points
General Category of U+180E is “Cf” (Format).
negative:
phase: parse
type: SyntaxError
features: [u180e]
--- |
650 |
| S7.2_A2.1_T2.js |
---
info: HORIZONTAL TAB (U+0009) may occur within strings
es5id: 7.2_A2.1_T2
description: Use real HORIZONTAL TAB
--- |
420 |
| S7.2_A2.2_T2.js |
---
info: VERTICAL TAB (U+000B) may occur within strings
es5id: 7.2_A2.2_T2
description: Use real VERTICAL TAB
--- |
416 |
| S7.2_A2.3_T2.js |
---
info: FORM FEED (U+000C) may occur within strings
es5id: 7.2_A2.3_T2
description: Use real FORM FEED
--- |
410 |
| S7.2_A2.4_T2.js |
---
info: SPACE (U+0020) may occur within strings
es5id: 7.2_A2.4_T2
description: Use real SPACE
--- |
402 |
| S7.2_A2.5_T2.js |
---
info: NO-BREAK SPACE (U+00A0) may occur within strings
es5id: 7.2_A2.5_T2
description: Use real NO-BREAK SPACE
--- |
426 |
| S7.2_A3.1_T2.js |
---
info: Single line comment can contain HORIZONTAL TAB (U+0009)
es5id: 7.2_A3.1_T2
description: Use real HORIZONTAL TAB
--- |
452 |
| S7.2_A3.2_T2.js |
---
info: Single line comment can contain VERTICAL TAB (U+000B)
es5id: 7.2_A3.2_T2
description: Use real VERTICAL TAB
--- |
448 |
| S7.2_A3.3_T2.js |
---
info: Single line comment can contain FORM FEED (U+000C)
es5id: 7.2_A3.3_T2
description: Use real FORM FEED
--- |
442 |
| S7.2_A3.4_T2.js |
---
info: Single line comment can contain SPACE (U+0020)
es5id: 7.2_A3.4_T2
description: Use real SPACE
--- |
434 |
| S7.2_A3.5_T2.js |
---
info: Single line comment can contain NO-BREAK SPACE (U+00A0)
es5id: 7.2_A3.5_T2
description: Use real NO-BREAK SPACE
--- |
460 |
| S7.2_A4.1_T2.js |
---
info: Multi line comment can contain HORIZONTAL TAB (U+0009)
es5id: 7.2_A4.1_T2
description: Use real HORIZONTAL TAB
--- |
455 |
| S7.2_A4.2_T2.js |
---
info: Multi line comment can contain VERTICAL TAB (U+000B)
es5id: 7.2_A4.2_T2
description: Use real VERTICAL TAB
--- |
451 |
| S7.2_A4.3_T2.js |
---
info: Multi line comment can contain FORM FEED (U+000C)
es5id: 7.2_A4.3_T2
description: Use real FORM FEED
--- |
445 |
| S7.2_A4.4_T2.js |
---
info: Multi line comment can contain SPACE (U+0020)
es5id: 7.2_A4.4_T2
description: Use real SPACE
--- |
437 |
| S7.2_A4.5_T2.js |
---
info: Multi line comment can contain NO-BREAK SPACE (U+00A0)
es5id: 7.2_A4.5_T2
description: Use real NO-BREAK SPACE
--- |
463 |
| S7.2_A5_T1.js |
---
info: |
White space cannot be expressed as a Unicode escape sequence consisting
of six characters, namely \u plus four hexadecimal digits
es5id: 7.2_A5_T1
description: Use TAB (U+0009)
negative:
phase: parse
type: SyntaxError
--- |
446 |
| S7.2_A5_T2.js |
---
info: |
White space cannot be expressed as a Unicode escape sequence consisting
of six characters, namely \u plus four hexadecimal digits
es5id: 7.2_A5_T2
description: Use VERTICAL TAB (U+000B)
negative:
phase: parse
type: SyntaxError
--- |
455 |
| S7.2_A5_T3.js |
---
info: |
White space cannot be expressed as a Unicode escape sequence consisting
of six characters, namely \u plus four hexadecimal digits
es5id: 7.2_A5_T3
description: Use FORM FEED (U+000C)
negative:
phase: parse
type: SyntaxError
--- |
452 |
| S7.2_A5_T4.js |
---
info: |
White space cannot be expressed as a Unicode escape sequence consisting
of six characters, namely \u plus four hexadecimal digits
es5id: 7.2_A5_T4
description: Use SPACE (U+0020)
negative:
phase: parse
type: SyntaxError
--- |
448 |
| S7.2_A5_T5.js |
---
info: |
White space cannot be expressed as a Unicode escape sequence consisting
of six characters, namely \u plus four hexadecimal digits
es5id: 7.2_A5_T5
description: Use NO-BREAK SPACE (U+00A0)
negative:
phase: parse
type: SyntaxError
--- |
457 |
| shell.js |
|
0 |
| string-form-feed.js |
---
info: FORM FEED (U+000C) may occur within strings
es5id: 7.2_A2.3_T1
description: Use FORM FEED(\u000C and \f)
--- |
617 |
| string-horizontal-tab.js |
---
info: HORIZONTAL TAB (U+0009) may occur within strings
es5id: 7.2_A2.1_T1
description: Use HORIZONTAL TAB(\u0009 and \t)
--- |
627 |
| string-nbsp.js |
---
info: NO-BREAK SPACE (U+00A0) may occur within strings
es5id: 7.2_A2.5_T1
description: Use NO-BREAK SPACE(\u00A0)
--- |
475 |
| string-space.js |
---
info: SPACE (U+0020) may occur within strings
es5id: 7.2_A2.4_T1
description: Use SPACE(\u0020)
--- |
584 |
| string-vertical-tab.js |
---
info: VERTICAL TAB (U+000B) may occur within strings
es5id: 7.2_A2.2_T1
description: Use VERTICAL TAB(\u000B and \v)
--- |
623 |