Add feature to disable top bar

[lomholdt]

• VSCode Version: Code 1.16.0 (787b31c, 2017-09-06T16:12:42.401Z)
• OS Version: Darwin x64 16.6.0
• Extensions:

Extension	Author (truncated)	Version
beautify	Hoo	1.1.1
vscode-docker	Pet	0.0.16
vscode-eslint	dba	1.3.1
php-intellisense	fel	1.5.1
phpcs	ika	0.7.0
php-docblocker	nei	1.2.0
vetur	oct	0.9.7
vscode-icons	rob	7.12.0
gitblame	wad	2.2.0

(1 theme extensions excluded)

---

Disabling tabs gives me nothing, since it still has one huge "Tab" at the top. Disabling tabs with "workbench.editor.showTabs": false only disables the tabs feature, it doesn't actually hide the top bar that's taking all the space. Even zen mode has the tabs.

Steps to Reproduce:

1. Disable tabs "workbench.editor.showTabs": false and watch the top bar appear

Reproduces without extensions: Yes/No

[ronjouch]

@bpasero @alexandrudima @chrmarti until such a feature is officially considered/implemented, is there a feature in electron/vscode similar to Firefox's userChrome.css that would let willing users to manually target and tweak/disable UI elements via custom/user-defined CSS?

In Firefox, I (and many other Firefox users enjoying the feature, there's even a subreddit for it!) routinely use this feature to #whatever-ui-component {display: none !important} the UX parts I don't use. Of course, that means I might kill the only entry point for an editor/extension UI component, and I'm okay with that. Is there something similar in Code?

EDIT okay, sorry for the noise, found existing feature request #459 - Support user stylesheet(s) and user script(s), 👍.

[vscodebot]

This issue has been closed because it is already tracked by another issue. See also our GitHub issues to search for existing issues and our issue reporting guidelines.

Happy Coding!

[ronjouch]

@bpasero can you point to the bug this one is a duplicate of? I searched for it and couldn't find it.

[bpasero]

@ronjouch you can use the label workbench-tabs to narrow down the search results and find it.

[ronjouch]

Found it, thank you. Passersby and subscribers of this bug, you should look at #33607.