Open Bug 867105 Opened 12 years ago Updated 2 years ago

EventSource connections should log error information to the Browser Console

Categories

(Core :: DOM: Core & HTML, defect, P5)

22 Branch
x86_64
Windows 7
defect

Tracking

()

People

(Reporter: djc, Unassigned)

Details

(Keywords: parity-chrome)

I was experimenting with server-sent events today. When I connect to a different server (actually the same server, but different port and with/without FQDN), the EventSource throws a generic error ("connection to <URL> was interrupted while the page was loading") only once the first event is sent by the server. I'm guessing the timing is related to bug 780396, as well. It would be pretty useful to have a specific error message clarifying that it's a CORS problem.
Whiteboard: [parity-chrome]
The script-detectable exception message itself shouldn't say much, but the console can have lots of detailed information.
The spec now has notes on reporting detailed error information to the console:

http://html5.org/tools/web-apps-tracker?from=7987&to=7988
Summary: EventSource connections should throw specific error for access violations on open → EventSource connections should log error information to the Browser Console
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome
Whiteboard: [parity-chrome]
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.