The car's browser does allow websockets, and I confirmed via https://www.websocket.org/echo.html. I was messing around a bit with the Pushbullet API to try to send notifications to a page loaded in the car's browser. I was able to build a very simple HTML/JavaScript page that connects to the Pushbullet websocket stream via JavaScript, and receive Pushbullet mirror notifications. I didn't have to do anything on a server, and Chrome allows the cross-origin websockets connection with no issue. The page works great on a desktop browser.
When I tried loading the page in the Model S web browser, it doesn't work. As you can imagine, it's a PITA to debug since there's no developer console in the car's browser and you can't see what's going on under the covers. After some "manual" debugging with code, it seems like it's not even ever making the websocket connection. It wouldn't fire any of the websocket events, except for the onclose event, and it fires with a readyState of 2.
At this point, my only guess as to why it doesn't work is because the car's browser won't allow cross-origin websocket connections. Has anyone experimented with websockets on the Model S browser? If so, have you encountered similar issues?
When I tried loading the page in the Model S web browser, it doesn't work. As you can imagine, it's a PITA to debug since there's no developer console in the car's browser and you can't see what's going on under the covers. After some "manual" debugging with code, it seems like it's not even ever making the websocket connection. It wouldn't fire any of the websocket events, except for the onclose event, and it fires with a readyState of 2.
At this point, my only guess as to why it doesn't work is because the car's browser won't allow cross-origin websocket connections. Has anyone experimented with websockets on the Model S browser? If so, have you encountered similar issues?