It looks like the arrows are no longer displaying correctly when inspecting elements.

I'm currently running Edge Version 80.0.320.4

What I see:

What is expected:

Clicking where the icon should be, the functionality is there so it seems like it's strictly a display issue.

Can u please make a theme for React DevTools? :)

Chrome added some new fields to the inspector and it seems like it broke a bit of this theme. Css text is now black on black, and some new fields are appearing as gray.

@ Menu Help / About Google Chrome:

Google Chrome is up to date
Version 66.0.3359.117 (Official Build) (64-bit)

 
Here's what I'm getting:

 
I also tested DevTools Theme: Zero Dark Matrix to make sure that the themes are working properly, didn't have any issues with it.

You know what i mean 🔪 🔫

Hi there!

I like your Magoon theme a lot but are using i3wm and openbox instead of gnome. I read that the theme was created by wal by accident. The fact that wal also can handle the colors for openbox I wanted to ask you if you could provide me the wallpaper which wal has extracted the colors for the Magoon theme so I can run it on my machine an get the colors for openbox as well...

This would be really nice!

How did you achieve that dark look?

OS：windows11
VScode：Version: 1.66.2 (user setup)
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-11T07:46:01.075Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Windows_NT x64 10.0.22000

statusbar and menu colorscheme seem to be not working

💻 Software

Visual Studio Code

🙋 Feature Request

As a DevOps engineer, I work extensively with the YAML language, but it doesn't seem to be supported. Everything is green: attributes, values, ... 😢

Exemple :

Title bar on Visual studio Code is dark grey and looks off from the rest of the theme in macOS.

Please add following color to give a much smoother and better looking theme!

"titleBar.activeBackground": "#232F39"
"titleBar.inactiveBackground": "#232F39"

In your instructions in the readme, you say to "go to chrome://flags/#enable-devtools-experiments and click enable," but you don't actually mention which specific experiment should be enabled. There is an extensive list of experiments there. It's possible that the page has changed since the last update to the readme.