W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[Bug 13525] New: Define what .origin should be for message events

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Aug 2011 18:51:35 +0000
To: public-webapps@w3.org
Message-ID: <bug-13525-2927@http.www.w3.org/Bugs/Public/>

           Summary: Define what .origin should be for message events
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Workers (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: jonas@sicking.cc
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org

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.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 2 August 2011 18:51:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 13:55:43 UTC