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

Cannot access SemiLight weight of Cascadia Code #103565

Closed
aaronbell opened this issue Jul 29, 2020 · 3 comments
Closed

Cannot access SemiLight weight of Cascadia Code #103565

aaronbell opened this issue Jul 29, 2020 · 3 comments
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@aaronbell
Copy link

  • VSCode Version: VS Code 1.47.3 & Insiders 1.48.0
  • OS Version: Mac OS 10.14.2 & Windows 10

Steps to Reproduce:

  1. Install the Cascadia Code TTF.
  2. Open VS Code Settings page and search for "Font Weight"
  3. Dropdown does not allow user to select "350" for SemiLight

The OpenType specification lists 'commonly-used' font weights, but any value between 1 and 1000 are actually considered valid. Use of a usWightClass of 350 for SemiLight is extremely common, including Microsoft's own Segoe UI SemiLight. VSCode should therefore support selection of "350". At current, users are not able to access Cascadia Code's SemiLight weight in VSCode. Other Microsoft products, such as Windows Terminal, are able to access this font weight without issue.

Additionally, as Cascadia Code is a variable font, users can (and should) be able to access any weight value between 200 and 700. I would suggest that, in addition to a drop down, you also enable "custom" values to be entered.

@IllusionMH
Copy link
Contributor

/duplicate of #101467 which has PR available, but no feedback from the team.

Just in case: you can use any text value e.g. "350" which will show warning, but works as expected

@aaronbell
Copy link
Author

Oh, thanks! I didn't find your issue when I searched.

@github-actions github-actions bot locked and limited conversation to collaborators Sep 12, 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)
Projects
None yet
Development

No branches or pull requests

3 participants
@IllusionMH @aaronbell and others