Open
Bug 867107
Opened 12 years ago
Updated 2 years ago
EventSource errors should log specifics to the Browser Console
Categories
(Core :: DOM: Core & HTML, defect, P5)
Tracking
()
NEW
People
(Reporter: djc, Unassigned)
Details
In the onerror callback on EventSource objects, I just get an [object Event] if I call toString() on the event (for example, in the case of a timeout). There doesn't seem to be any other identifiable information on the object, either. See also bug 867105, where the CORS error is completely opaque as well.
Comment 1•12 years ago
|
||
Please file a spec bug. https://www.w3.org/Bugs/Public/enter_bug.cgi?product=WHATWG http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#the-eventsource-interface defines that error event is a simple event.
Reporter | ||
Comment 2•12 years ago
|
||
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21876 (Made a stupid error in my description there. Will try to fix it as soon as I figure out how to create an account there.)
Comment 3•11 years ago
|
||
The opacity at the script level is intentional, but nothing prevents the console from having lots and lots of detailed debugging info.
Reporter | ||
Comment 4•11 years ago
|
||
The spec now has notes on reporting detailed error information to the console: http://html5.org/tools/web-apps-tracker?from=7987&to=7988
Reporter | ||
Updated•11 years ago
|
Summary: EventSource errors should come with a specific error message → EventSource errors should log specifics to the Browser Console
Comment 5•6 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•