Connect Failed from Web IDE

My issue was a different one, but this seems to be the right place to consolidate.

1. I pick the correct port, click the connect button, and get "Connect Failed".
   
2. I am in the dialup group, and picocom --baud 9600 --flow n /dev/ttyACM0 works great
   
3. After a while, the red LED comes on and stays lit. But this makes no difference to 1 & 2.
   
   

In my case, I found that the problem went away when downgrading from Chrome Beta (34.0.1847.60-1) to Chrome stable (33.0.1750.152-1). Relevant parts from the debug log:

[14715:14715:0315/082109:INFO:CONSOLE(65­)] ">>> Connecting", source: chrome-extension://bleoifhkdalbjfbobjack­fdifdneehpo/js/espruino_status.js (65)
[14715:14715:0315/082109:INFO:CONSOLE(18­5)] "Set Slow Write = true", source: chrome-extension://bleoifhkdalbjfbobjack­fdifdneehpo/js/espruino_serial.js (185)
[14715:14715:0315/082109:INFO:CONSOLE(58­)] "Unable to open device (connectionInfo=undefined)", source: chrome-extension://bleoifhkdalbjfbobjack­fdifdneehpo/js/espruino_serial.js (58)
[14715:14715:0315/082109:INFO:CONSOLE(65­)] ">>> Connect Failed.", source: chrome-extension://bleoifhkdalbjfbobjack­fdifdneehpo/js/espruino_status.js (65)

It turns out, that this is because in chrome beta/34, the device names are being reported without /dev/. An easy fix, if you want to run beta, is to use the dev version of Espruino IDE (from github, installed as unpacked), right-click on the port name, inspect the option element, and change the value to include /dev/. As best I can tell, it's a chrome bug, so probably not worth working around this in EspruinoIDE until we know more (according to the API, getDevices() should return paths that can be used in connect(), and that doesn't seem to be true at the moment). Possibly related to chromium #334698.