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

Latest update to 1.43.0 broke color theme "Atom One Dark" #92335

Closed
CombeeMike opened this issue Mar 10, 2020 · 10 comments
Closed

Latest update to 1.43.0 broke color theme "Atom One Dark" #92335

CombeeMike opened this issue Mar 10, 2020 · 10 comments
Labels
*duplicate Issue identified as a duplicate of another issue(s) semantic-tokens Semantic tokens issues typescript Typescript support issues

Comments

@CombeeMike
Copy link

  • VSCode Version: 1.43.0
  • OS Version: Win 10 v1909

Steps to Reproduce:

  1. Download & activate theme Atom One Dark
  2. Tokens are colorized different then in previous versions
  3. In "side by side" diff view, correct colors are shown on the left side (the original):

2020-03-10_10h25_27

Some more observations:

  • When activating the theme, it appears "normal" for a moment and changes shortly after
  • Same after starting VSCode. The colorization is initially correct and changes once the status message "Initializing JS/TS language features" disappears

2020-03-10_10h36_02

Does this issue occur when all extensions are disabled?: No, since the theme is not loaded then ;)

Also happens in fresh installation of VS Code insider with only Atom One Dark extension installed.

@vscodebot
Copy link

vscodebot bot commented Mar 10, 2020

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@themeler
Copy link

I've the same problem (Base16 Tomorrow Dark theme). Colors are completly messed up.

@cuddeford
Copy link

This is also happening for me with Ruby Blue

@janos-kasa
Copy link

This comment helped me: #92308 (comment)

Themes need to be updated to support semantic highlighting.

@cuddeford
Copy link

The workaround worked for me

@CombeeMike
Copy link
Author

Works for me as well. Am I correct in assuming that the theme maintainer need to update their themes to work with the new semantic highlighting as well?

@cuddeford
Copy link

Works for me as well. Am I correct in assuming that the theme maintainer need to update their themes to work with the new semantic highlighting as well?

As far as I can tell, yes. Here's is some reference reading: https://github.com/microsoft/vscode/wiki/Semantic-Highlighting-Overview

@Whitefox98
Copy link

Same problem

@rebornix
Copy link
Member

thank you all for feedback, let's track this issue in #92308 and for now you can turn off the semantic syntax highlighting feature by changing below setting:

"editor.semanticHighlighting.enabled": false

@rebornix rebornix added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 10, 2020
@vscodebot
Copy link

vscodebot bot commented Mar 10, 2020

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Mar 10, 2020
@aeschli aeschli added semantic-tokens Semantic tokens issues typescript Typescript support issues labels Mar 11, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) semantic-tokens Semantic tokens issues typescript Typescript support issues
Projects
None yet
Development

No branches or pull requests

7 participants