vscode: [Insiders]: Typescript Syntax highlight is broken
Issue Type: Bug
- Open typescript file
- See that syntax highlight is broken
However, if I’m switching custom token color for scope: entity then any white token gets color of this customization.
Without token color customization
With token color customization:
VS Code version: Code - Insiders 1.42.0-insider (c4d53a19df8799f5d49a4f49a6900c499e6fa27c, 2020-01-23T06:38:09.164Z) OS version: Linux x64 5.3.0-26-generic snap
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 5 2600 Six-Core Processor (12 x 1477) |
| GPU Status | 2d_canvas: unavailable_software flash_3d: disabled_software flash_stage3d: disabled_software flash_stage3d_baseline: disabled_software gpu_compositing: disabled_software multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: disabled_off rasterization: disabled_software skia_renderer: disabled_off_ok video_decode: disabled_software viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: unavailable_software webgl2: unavailable_software |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 31.38GB (12.20GB free) |
| Process Argv | –force-user-env --no-sandbox --unity-launch --no-sandbox |
| Screen Reader | no |
| VM | 0% |
Extensions (2)
| Extension | Author (truncated) | Version |
|---|---|---|
| todo-tree | Gru | 0.0.166 |
| sass-indented | syl | 1.7.3 |
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 4
- Comments: 17 (6 by maintainers)
The same for pure JavaScript. Also sometimes the highlight returns to normal, secondarily, as if “flickering”
One more thing: highlighting is normal initially, when opening VSCode Insiders, but becomes broken after like 1-2 seconds. And after changing the settings of token color customizations it flickers to normal for like 0.5 seconds and becomes broken again 😃
@limbosounds Sorry, I didn’t realize that ‘Without token color customization’ is also broken. I don’t know your theme. What is the expected result? Please make sure to update to the latest i-build (1.42.0-insider, 35116fa958d6622df1c31b4d84810b999a858170). There has been some fixes.