[Webkit-unassigned] [Bug 119974] New: [eventsource] If there is a network error, the readyState of eventsource got CONNECTING but not CLOSED.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Aug 18 00:40:57 PDT 2013


https://bugs.webkit.org/show_bug.cgi?id=119974

           Summary: [eventsource] If there is a network error, the
                    readyState of eventsource got CONNECTING but not
                    CLOSED.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: tina.zhao at intel.com


[ServerSentEvent]
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36

Steps to reproduce:
According to the spec description, if there is a network error, the readyState is expected as 2 (CLOSED).

Spec Info: Server-Sent Events Candidate Recommendation 11 December 2012  (http://www.w3.org/TR/2012/CR-eventsource-20121211/ ).
Spec Description:
"CLOSED (numeric value 2)
The connection is not open, and the user agent is not trying to reconnect. Either there was a fatal error or the close() method was invoked."

- Test wiki: http://www.w3.org/wiki/Webapps/Interop/ServerSentEvents
- Test suite: https://github.com/w3c/web-platform-tests/tree/master/eventsource
- Test case: http://w3c-test.org/web-platform-tests/master/eventsource/shared-worker/eventsource-constructor-non-same-origin.htm

Actual results:
Assersion failed: assert_equals: source.readyState expected 2-CLOSED but got 0-CONNECTING.
This test Failed on Chrome 28.0.1500.95 m, got PASS on Opera Next 12.16

Expected results:
In this case, readyState is expected 2-CLOSED.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list