Closed cope closed 10 years ago
I filed a firefox bug (https://bugzilla.mozilla.org/show_bug.cgi?id=949376) for this, since I do not believe that this is a web-socket-js issue.
ups... https://developer.mozilla.org/zh-CN/docs/Mozilla/Firefox/Releases/26/Site_Compatibility
MessageEvent has been updated
Bug 848294 – Update MessageEvent to be compatible with the spec
The MessageEvent interface has been updated to comply with the latest spec. The initMessageEvent method has been removed while the interface is now a constructor.
found a solution
if (event.initMessageEvent) { // IE does not accept 'new MessageEvent' so this has to stay event.initMessageEvent("message", false, false, data, null, null, window, null); } else if (event.initEvent) { // needed for FF 26 and possible others soon... var event = new MessageEvent('message', { 'view': window, 'bubbles': false, 'cancelable': false, 'data': data }); }
Since FF 26 this error message started showing up, crashing the application.
I believe event.initMessageEvent is only called in web_socket.js on line 208?