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.
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+
Whiteboard: [WebRTC] [blocking-webrtc-]
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.