3 ms·
This is related to some issue with Safari's new WebGL 2 implementation they shipped recently[1]. Currently we disable the webgl renderer on Safari inside github
by Tyriar 5y ago
This is related to some issue with Safari's new WebGL 2 implementation they shipped recently[1]. Currently we disable the webgl renderer on Safari inside github.dev/codespaces to work around this.
[1]: https://github.com/xtermjs/xterm.js/issues/3357 https://github.com/xtermjs/xterm.js/issues/3357
- messe 5y agoLooks to be the case. Disabling WebGL 2.0 at the browser level fixes the issue.