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

After disabling a VSIX extension, the extension shows dimmed in the "ENABLED" list #67369

Closed
weinand opened this issue Jan 29, 2019 · 4 comments
Assignees
Labels
extensions Issues concerning extensions *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach

Comments

@weinand
Copy link
Contributor

weinand commented Jan 29, 2019

Issue Type: Bug

Testing #67231

For testing #67231 I had to create a VSIX from a non-code extension and installed it.
After disabling it, the extension continued to show up in the "ENABLED" view of the extension viewlet, albeit in a dimmed style.

2019-01-29_12-08-07

VS Code version: Code - Insiders 1.31.0-insider (acc7365, 2019-01-29T06:13:57.866Z)
OS version: Darwin x64 18.2.0

System Info
Item Value
CPUs Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2900)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 1, 1, 1
Memory (System) 32.00GB (9.24GB free)
Process Argv
Screen Reader no
VM 0%
Extensions: none
@weinand
Copy link
Contributor Author

weinand commented Jan 29, 2019

Another instance of the problem:

2019-01-29_13-00-47

@sandy081
Copy link
Member

@weinand Disabled extensions are dimmed by default. That's why it is dimmed. But it was still shown in Enabled section because removing the entry as soon as you perform an action might not be good user experience? Views get updated once you switch views.

@sandy081 sandy081 added the extensions Issues concerning extensions label Jan 29, 2019
@weinand
Copy link
Contributor Author

weinand commented Jan 29, 2019

A good user experience would be if the disabled extension would move from the Enabled to the Disabled section. This would require that both sections are visible.
But keeping it under Enabled looks just broken.

@sandy081 sandy081 added the under-discussion Issue is under discussion for relevance, priority, approach label Jan 29, 2019
@sandy081 sandy081 added this to the February 2019 milestone Jan 29, 2019
@sandy081 sandy081 removed this from the February 2019 milestone Feb 21, 2019
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Dec 6, 2022
@vscodenpa
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions Issues concerning extensions *out-of-scope Posted issue is not in scope of VS Code under-discussion Issue is under discussion for relevance, priority, approach
Projects
None yet
Development

No branches or pull requests

4 participants