13525 2011-08-02 18:51:34 +0000 Define what .origin should be for message events 2011-08-08 21:43:36 +0000 1 1 1 Unclassified WebAppsWG WebSocket API (editor: Ian Hickson) unspecified PC All RESOLVED FIXED P2 normal --- 1 jonas ian ian mcmanus mike public-webapps public-webapps-bugzilla oldest_to_newest 52002 0 jonas 2011-08-02 18:51:34 +0000 Right now the websocket protocol doesn't say what event.origin should return for message events fired for incoming data, which I believe implicitly means that it should be the empty string. It seems nice if it was more consistent with EventSource which uses the origin of the server we're connected to. 52014 1 jonas 2011-08-02 22:01:35 +0000 Oops, wrong component. 54401 2 ian 2011-08-08 21:16:39 +0000 http://www.whatwg.org/specs/web-apps/current-work/complete.html#messageevent defines the default as being the empty string, yes. What origin would you want it set to? Web Sockets by definition are same-origin with whatever script created them (they don't connect successfully otherwise). I suppose we could parse WebSocket.url and set MessageEvent.origin to the scheme, host, and port parts of that URL, but that seems a bit awkward (and wouldn't really be an origin in the technical sense). 54403 3 jonas 2011-08-08 21:24:11 +0000 Why wouldn't that be a origin in the technical sense? 54407 4 ian 2011-08-08 21:41:12 +0000 We talked about this on IRC. I'll do what EventSource does (it also doesn't use what is technically the origin, but this is mostly a matter of how you view things and if it'll help authors, why not expose it). 54408 5 contributor 2011-08-08 21:43:36 +0000 Checked in as WHATWG revision r6386. Check-in comment: Make event.origin for WebSockets work like it does for EventSource, for consistency. http://html5.org/tools/web-apps-tracker?from=6385&to=6386