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 be used with Microsoft Edge #15

Open
fu-sen opened this issue Jan 29, 2020 · 3 comments
Open

Cannot be used with Microsoft Edge #15

fu-sen opened this issue Jan 29, 2020 · 3 comments

Comments

@fu-sen
Copy link

@fu-sen fu-sen commented Jan 29, 2020

My BBS buddies tried sshwifty and found this.
He did not use GitHub, so I issued an issue on my behalf.

When you select Telnet or SSH from sshwifty in Microsoft Edge,
the following screen appears and you cannot use it:
スクリーンショット 2020-01-29 10 40 54

サイトからのメッセージ = Message from site

In addition, when using Internet Explorer, it stops at the boot screen,
but I think that this need not be considered.
But Edge support will need to be considered for Windows users.

@niruix

This comment has been minimized.

Copy link
Owner

@niruix niruix commented Jan 29, 2020

Can you ask your buddy to upgrade their web browser to maybe the newest one which based on WebKit?

If the web browser does not support TextEncoder (Which is introduced more than 5 years ago), then it probably won't support many other APIs Sshwifty requires.

@fu-sen

This comment has been minimized.

Copy link
Author

@fu-sen fu-sen commented Jan 29, 2020

Yes. Because my main browser is Chrome. I can understand.
Looking at what it doesn't support right now, it won't be easy.
(Especially if you are using Mac or Linux)

Some may have the same opinion. This issue may need to be left open.
When closed, the same issue may come later.

@niruix

This comment has been minimized.

Copy link
Owner

@niruix niruix commented Jan 29, 2020

It's not just not easy, it's basically impossible.

Sshwifty uses many JavaScript APIs which is not exist in Internet Exporter and Edge, and there are no replacement (polyfill) for many of those APIs.

The web development has moved a long way during these 5 years, keep the web browser updated is the only way out.

Also, a side note: Old web browser are insecure, especially when it comes to Internet Explorer. I'd personally recommend everybody to upgrade to a new one as soon as possible for ones own online safety.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.