-
Notifications
You must be signed in to change notification settings - Fork 36.5k
Closed
Labels
javascriptJavaScript support issuesJavaScript support issueslanguages-basicBasic language support issuesBasic language support issuestypescriptTypescript support issuesTypescript support issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)
Description
- VSCode Version: Code 1.12.2 (19222cd, 2017-05-10T13:13:11.413Z)
- OS Version: Darwin x64 16.7.0
- Extensions:
| Extension | Author | Version |
|---|---|---|
| output-colorizer | IBM | 0.1.1 |
| material-icon-theme | PKief | 2.0.6 |
| vscode-theme-onedark | akamud | 1.3.2 |
| monokai-plusplus | dcasella | 1.6.0 |
| githistory | donjayamanne | 0.2.0 |
| theme-dracula | dracula-theme | 1.17.0 |
| php-intellisense | felixfbecker | 1.2.2 |
| ftp-sync | lukasz-wronski | 0.3.3 |
| typescript-javascript-grammar | ms-vscode | 0.0.20 |
| language-stylus | sysoev | 1.7.3 |
| twig | whatwedo | 1.0.2 |
| Material-theme | zhuangtongfa | 2.8.0 |
Steps to Reproduce:
- Create a new JavaScript document
- Enter a single line comment using // and some text, then on any new line below without entering any other text, create a multi-line comment using /* and */
The expected result is that the syntax highlighting shows that they're both comments by placing them both in one color, however the actual result is that the second (multi-line) comment is not treated as a comment by the syntax highlighting. Placing text between the two comments fixes the issue

Metadata
Metadata
Assignees
Labels
javascriptJavaScript support issuesJavaScript support issueslanguages-basicBasic language support issuesBasic language support issuestypescriptTypescript support issuesTypescript support issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)
