Cannot read property 'features' of undefined - while using ligatures addon
See original GitHub issueThis bug is caused in https://github.com/princjef/font-ligatures which is a dependency of the ligatures addon.
For some fonts, the gsub
table may not be present. And that causes the below error.
It causes the rendering of the font to stop working.
Ref- https://github.com/vercel/hyper/issues/4360#issuecomment-605370067 & https://github.com/vercel/hyper/issues/3391#issuecomment-624081818
I’ve opened a pull request for it https://github.com/princjef/font-ligatures/pull/18 but that repo seems inactive.
Would it be possible to use some other module or incorporate this (font-ligature) module’s code into the the xterm-addon-ligatures?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
app.js:12 Uncaught TypeError: Cannot read properties of ...
So, we use classList for add new class in html element. Share.
Read more >Documentation - TypeScript 3.7
Note that if bar is null or undefined , our code will still hit an error ... The ?? operator can replace uses...
Read more >Release Log - Overview | Learnosity Reference
Fixed a bug where a Cannot read properties of undefined error would be thrown when a Question's attempt status changed. Fixed a bug...
Read more >Safari Technology Preview Release Notes - Apple Developer
Added support for editing @-rules in the Styles sidebar of the Elements tab ... Fixed blob URLs with a fragment from opaque origins...
Read more >Bug listing with status UNCONFIRMED as at 2022/12/24 17 ...
Full-featured Bitcoin client, offering a dozen innovative features. ... Alternate version of fonts with graphite ligatures" status:UNCONFIRMED resolution: ...
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
Hey folks, sorry for the delay on the upstream fix. It has been merged and published in version 1.3.3, so this issue should be resolved now. Let me know if this is not the case
@princjef thanks for the quick fix mate 🙂