terminalWidth and terminalHeight are undefined

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open latest Firefox/Chrome
2. Open Firebug/Inspector Window
3. Open ShellInABox session
4. Examine network requests; note that you can only see 0-2 lines in the 
ShellInABox session, depending on browser

This uses the latest version, 2.11.

These are the network requests sent:
http://withg.us.to:4200/?&height=undefined&rooturl=http%3A%2F%2Fwithg.us.to%3A42
00%2F&width=undefined
{"session":"uTkjvpyik12oLWGVWxo/eQ","data":""}

http://withg.us.to:4200/?&height=undefined&session=uTkjvpyik12oLWGVWxo%2FeQ&widt
h=undefined
[no response]

As you can probably tell, http://withg.us.to:4200/ is my server with a live 
ShellInABox daemon running. (I'd like to remove the server URL and such when 
this bug is fixed for security.) Feel free to take a look at it.

The command used to launch:
albert@withgusto:~/shellinabox-2.11/shellinabox$ sudo shellinaboxd -s "/:LOGIN" 
-s [redacted] -s [redacted] -s [redacted] --disable-ssl --css white-on-black.css

Original issue reported on code.google.com by alberthr...@gmail.com on 8 Apr 2012 at 3:54

[GoogleCodeExporter]

Also, I've tried to disable some extensions to no avail.
I've also cleared cookies and cache without any success.
And of course, I've tried restarting the daemon.

Here's a screenshot that may shed some light on this issue.

Original comment by alberthr...@gmail.com on 8 Apr 2012 at 4:03

Attachments:

• ShellInABoxFail.PNG

[GoogleCodeExporter]

Have a similar problem. Firefox and Chrome both just show a very thin line. 
Dimensions are reported as "undefined".

Connection is SSL but running via a proxy server. Can network timeouts have an 
influence?
A different machine on the same network and with same browser version work. But 
failing machine has a persistent failure.

Original comment by osm.tool...@gmail.com on 14 Sep 2012 at 1:04

Attachments:

• ScreenShot128.png

[GoogleCodeExporter]

Having the same issue with Internet Explorer 9.0.8112.16421 on my school's 
computers. I used a proxy to serve http://myserver:4200 as 
http://myserver:80/shell because most ports are blocked at my school. 

Original comment by Habstinat on 15 Oct 2012 at 2:31