Screen distorted when opening the 'View Tokens' menu

[vieiraes]

Type: Bug

• Open a Visual Studio Code theme repository
• Press F5 to start the color preview mode
• Go to the VS Code instance that opened with F5
• Select 'Inspect Tokens' to check the color of a theme item
• In the displayed window, it should show the token description, properties, and colors, but it displays a completely misconfigured screen

VS Code version: Code 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d, 2023-11-01T11:28:21.782Z) OS version: Linux x64 5.15.0-87-generic Modes:

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz (8 x 2300)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|2, 2, 2| |Memory (System)|15.23GB (5.02GB free)| |Process Argv|--unity-launch --crash-reporter-id 2613244b-fb5b-44bf-b2e7-8bf5fc6b7271| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|ubuntu| |XDG_CURRENT_DESKTOP|Unity| |XDG_SESSION_DESKTOP|ubuntu| |XDG_SESSION_TYPE|x11|

Extensions (25)

Extension|Author (truncated)|Version ---|---|--- aws-toolkit-vscode|ama|1.96.0 sidebar-markdown-notes|ass|1.2.0 npm-intellisense|chr|1.4.5 path-intellisense|chr|2.8.5 vscode-dashboard-window-colors|Dan|2.7.3 gitlens|eam|14.4.0 auto-rename-tag|for|0.1.10 vscode-pull-request-github|Git|0.74.0 plantuml|jeb|2.17.5 rainbow-csv|mec|3.8.0 git-graph|mhu|1.30.0 dotenv|mik|1.0.1 vscode-docker|ms-|1.26.1 vscode-language-pack-pt-BR|MS-|1.83.2023101109 emoji|Per|1.0.1 postman-for-vscode|Pos|0.12.1 vscode-xml|red|0.26.1 vscode-yaml|red|1.14.0 LiveServer|rit|5.7.9 html5-boilerplate|sid|1.1.1 pdf|tom|1.2.2 quokka-vscode|Wal|1.0.575 vscode-todo-highlight|way|1.0.5 markdown-pdf|yza|1.5.0 markdown-all-in-one|yzh|3.5.1 (1 theme extensions excluded)

A/B Experiments

``` vsliv368:30146709 vsreu685:30147344 python383cf:30185419 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256860 vslsvsres303:30308271 vserr242:30382549 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vsdfh931:30280409 vshan820:30294714 vstes263:30335439 vscoreces:30445986 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593:30376534 pythonvs932:30410667 py29gd2263cf:30856253 vsclangdf:30486550 c4g48928:30535728 dsvsc012cf:30540253 pynewext54:30695312 azure-dev_surveyone:30548225 282f8724:30602487 f6dab269:30613381 showlangstatbar:30737416 pythonfmttext:30731395 fixshowwlkth:30771522 showindicator:30805244 pythongtdpath:30769146 i26e3531:30792625 pythonnosmt12:30797651 pythonidxpt:30866567 pythonnoceb:30805159 synctok:30869157 dsvsc013:30795093 dsvsc014:30804076 dsvsc015:30845448 pythontestfixtcf:30871695 pythonregdiag2:30871582 pythonmypyd1:30879173 pythoncet00cf:30874137 pythontbext0:30879054 ```

[aeschli]

I'm not able to reproduce. Maybe related to a font setting? Can you reproduce on an empty profile?

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!