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

Chrome shows blank after log in #2

Open
bbhenry opened this issue Jun 14, 2013 · 3 comments
Open

Chrome shows blank after log in #2

bbhenry opened this issue Jun 14, 2013 · 3 comments

Comments

@bbhenry
Copy link

bbhenry commented Jun 14, 2013

I am using the latest Chrome and once I log in with my ssh credential, that web page is blank with only the WSSH title bar left on top of the page. And I tested with Firefox which works fine.

Is there a way to adjust the terminal size? Font size?

Thanks,

Henry

@aluzzardi
Copy link
Owner

There might be an error in the JS code that prevents the page to load.

Could you open the Javascript Console of Chrome and try to reload the page?
It should give you the error description.

Thanks,

  • A

@mrijken
Copy link

mrijken commented Jul 4, 2013

The error I get in the console is:

Refused to execute script from 'https://raw.github.com/chjj/tty.js/36717df8e96f35f4e2bd3fd585e9361f1439fc7e/static/term.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.

@mculhane
Copy link

Apparently Chrome used to ignore MIME types until recently, but now Chrome does MIME type checking. As a result, Chrome refuses to execute stuff on raw.github.com (which has the non-executable type 'text/plain').

I was able to get rid of the error by downloading the file and linking to it locally. Once I did that, the terminal popped back up in Chrome and everything worked just fine.

Alternatively, some clever folks seem to have come up with https://rawgithub.com, which simply serves content from https://raw.github.com with the proper content types (though it's not to be used in production environments). So, just removing the first dot in the script URL should fix the issue as well.

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

No branches or pull requests

4 participants