Remote font error on Edge browser about sshwifty HOT 7 CLOSED

Hi.

Please try reload the page, and see if the problem persisted.

The error might occur when the remote font failed to load within a per-determined time limit. Under normal situation, the font is still being loaded, just taking a longer time than expected, causing Sshwifty to use fallback fonts (and display that warning message to notify the user). The warning should disappear after the font is loaded.

from sshwifty.

Hi.

Please try reload the page, and see if the problem persisted.

The error might occur when the remote font failed to load within a per-determined time limit. Under normal situation, the font is still being loaded, just taking a longer time than expected, causing Sshwifty to use fallback fonts (and display that warning message to notify the user). The warning should disappear after the font is loaded.

Unfortunately that doesn't work. It persists, and appears every single time I log into my SSH target. Again, every other browser works fine, just Edge strangely.

Console throws up this:

from sshwifty.

Maybe it's the WebGLAddon for xterm.js that is causing this problem.

Can you privide the version of your Edge browser and OS? I tested one that I have but that one don't seemed to trigger the error.

Thanks!

from sshwifty.

Maybe it's the WebGLAddon for xterm.js that is causing this problem.

Can you privide the version of your Edge browser and OS? I tested one that I have but that one don't seemed to trigger the error.

Thanks!

Microsoft Edge
Version 120.0.2210.121 (Official build) (64-bit)
Microsoft Windows 11
Version 23H2 Build 22631.2861

from sshwifty.

Update: Error does NOT appear on
Microsoft Edge
Version 122.0.2325.0 (Official build) canary (64-bit)

from sshwifty.

Edge is probably still trying to implement WebGL related features.

Regardless, I will still fix my part of the issue. But it might take a few days since I need to setup a Windows 11 environment first. I'll keep you posted if any update on this is available.

Thanks again for reporting.

from sshwifty.

Hi, I've released version 0.3.6-beta, which should address this problem.

I'll close this issue for now, if the problem still occurs for you, please reopen it and report back. Thanks!

from sshwifty.