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

Annoying "[Unsupported]" suffix in the titlebar #30556

Closed
fabiospampinato opened this issue Jul 13, 2017 · 5 comments
Closed

Annoying "[Unsupported]" suffix in the titlebar #30556

fabiospampinato opened this issue Jul 13, 2017 · 5 comments
Assignees
Labels
*as-designed Described behavior is as designed

Comments

@fabiospampinato
Copy link
Contributor

The "[Unsupported]" suffix in the titlebar is pretty annoying.

In my case it's there because I use the Custom CSS and JS Loader extension, just for removing some stuff I don't use via CSS.

I understand why it's there, but I'd like to have a way to remove it.

Perhaps a window.titleShowUnsupported setting?
Perhaps add it via a ${unsupported} placeholder under the window.title setting?

@bpasero
Copy link
Member

bpasero commented Jul 13, 2017

As we do not support extensions that patch our bits on disk, we would not want to push a change that reverts this UI annoyance. Please uninstall this extension.

@bpasero bpasero closed this as completed Jul 13, 2017
@bpasero bpasero added the *as-designed Described behavior is as designed label Jul 13, 2017
@fabiospampinato
Copy link
Contributor Author

fabiospampinato commented Jul 13, 2017

I think I should be able to run any extension I choose, whether you "support" it or not, without having VSC explicitly behaving differently because of it.

I wish VSC was more hackable, like Atom. The ability to load a custom CSS file is pretty important to me.

Btw, if anybody else finds it annoying I made an extension for removing it.

@Kaffiend
Copy link

I removed the extension and the preference and its still there..

@Kaffiend
Copy link

had to reinstall.

@peteplays
Copy link

I agree 💯 with @fabiospampinato. If vscode does not want thier bits messed with, they need to support more robust custom theming options. I am using Custom CSS and JS Loader as a temp workaround with the hopes that an option like this will be rolled out as part of vscode 👈 @bpasero

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed
Projects
None yet
Development

No branches or pull requests

4 participants