Template color highlighting broke
See original GitHub issueDescribe the bug
Tag highlighting is strange and inconsistent
Expected behavior
opening tags and closing tags should have the same color. No error red should be shown if code is correct.
Screenshots
Additional context
worked in v0.900.5
, broken in v0.900.6
Issue Analytics
- State:
- Created 4 years ago
- Reactions:66
- Comments:46 (18 by maintainers)
Top Results From Across the Web
syntax highlighting for vue templates broke after 16.8 update
Before the update, the html within the <script> tag would be properly highlighted. After the 16.8 update, it's all white. I need this...
Read more >Syntax highlighting broken in vscode (JS) - Stack Overflow
I'm on a new M1 macbook, and I've tried updating to the latest vscode, switching to vanilla color themes, nothing works, anything else...
Read more >Syntax Highlighting - GitLab Docs
GitLab provides syntax highlighting on all files through Highlight.js and the Rouge Ruby gem. It attempts to guess what language to use based...
Read more >Syntax Highlighting and Code Completion not working after ...
As written in the title, Syntax Highlight and Code Completion features are broke down after the theme change.
Read more >Syntax Highlighting Colorschemes - Atelierbram
Collection of colorschemes for Code Syntax highlighting. ... “DuoTone themes use only 2 hues (7 shades in total). It tones down less important...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes.
In addition to the above, the comment shortcut such as
ctrl + /
/cmd + /
produces a typescript-like comment// ...
instead of html-like comment<!-- ... -->
The issue is really annoying and makes the extension instead of being helpful to be absolutely unusable.
My guess: this is somehow related to custom structural directives such as e.g. angular material ones and / or
(event)
handlers.Here are the versions