Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading icon is not showing for slow tree nodes #95878

Closed
IllusionMH opened this issue Apr 22, 2020 · 0 comments · Fixed by #95885
Closed

Loading icon is not showing for slow tree nodes #95878

IllusionMH opened this issue Apr 22, 2020 · 0 comments · Fixed by #95885
Assignees

Comments

@IllusionMH
Copy link
Contributor

Issue Type: Bug

In latest Insiders build instead of loading icon I see spinning chevron for some tree nodes.
It's mostly noticeable in GitHub Pull Request extension tree, however I was able to reproduce it in Call Hierarchy while expanding some nested trees.

Looks like .codicon-loading:before has lower priority than .codicon-tree-item-expanded:before which prevents icon change.

/cc @aeschli

VS Code version: Code - Insiders 1.45.0-insider (9328b32, 2020-04-22T08:44:55.510Z)
OS version: Windows_NT x64 10.0.18363

System Info
Item Value
CPUs Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)
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) undefined
Memory (System) 31.72GB (16.46GB free)
Process Argv
Screen Reader no
VM 0%
Extensions: none
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants