Font rendering weight heavier than in 2.x
See original GitHub issueIt looks like the font weight rendering in the 3.x branch is much heavier than in the 2.x branch even with fontWeight
set to 100
, normal
or nothing. When setting fontWeight
to bold
the text is more bold so it appears that the config value is being respected.
2.x
3.3
3.3 (fontWeight: 'bold'
)
const term = new XTerm({
fontWeight: '100',
fontFamily: 'ubuntu mono',
theme: {
background: '#111'
}
});
I’m using https://www.npmjs.com/package/xterm-webfont to load the webfont however the weight is consistent without it.
This is also consistent in both the latest Chrome and Firefox.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Fonts are Heavier in v2.0 · Issue #2856 · vercel/hyper - GitHub
After updating to v2.0 I noticed that the font rendering is heavier than before. I've tried changing the fontWeight setting to either ...
Read more >font-weight - CSS: Cascading Style Sheets - MDN Web Docs
One relative font weight heavier than the parent element. Note that only four font weights are considered for relative weight calculation; see ...
Read more >Html5 canvas font weight is rendering much heavier than it ...
I have set in my code that the text should render in Gotham at a 'regular' weight but it seems to be rendering...
Read more >font-weight | CSS-Tricks
The font-weight property sets the weight, or thickness, of a font and is dependent either on available font faces within a font family...
Read more >Introduction to variable fonts on the web
When we have fewer pixels for rendering the glyph, a two bar design can become illegible. To combat this, much like the Italic...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@bgw Here is 3.3.0 with
term.setOption('allowTransparency', true)
. There doesn’t appear to be any change with or without it enabled (In both Chrome and Firefox).We’re moving towards DOM and webgl renderers in favor of the canvas one.