Closed Bug 843625 Opened 11 years ago Closed 2 years ago

DataChannels need better error reporting for edge-case handling

Categories

(Core :: WebRTC: Networking, defect, P4)

Product:
Core
Component:
WebRTC: Networking
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: jesup, Assigned: jesup)

References

Details

There are several edge cases where you have transmission failures, etc that need to report errors to the application via onError; these are not currently hooked up.  Most of these are far-out edge cases or ones where there's little the app can do.
Depends on: 842126
Going to talk about this on Friday's meeting, but as a quick note:

We need to be careful that we don't have too many of these error reporting bugs. Too many = a very bad developer experience, as new developers to the API will hit a lot more difficulty trying to figure out how to get started with the APIs. Besides the fact there's also the factor of helping web devs provide correct fallback behavior on error cases, as well.
Agreed.  These are mostly far-out-almost-impossible edge cases
backlog: --- → webRTC+
Rank: 35
Whiteboard: [WebRTC] [blocking-webrtc-]
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.