Closed
Bug 842908
Opened 11 years ago
Closed 11 years ago
Calling createAnswer on a Peer Connection immediately after creation - error callback fires with "3", should be "INVALID_STATE"
Categories
(Core :: WebRTC, defect)
Core
WebRTC
Tracking
()
RESOLVED
DUPLICATE
of bug 834270
People
(Reporter: jsmith, Unassigned)
Details
Attachments
(1 file)
170 bytes,
text/html
|
Details |
Steps: 1. Load the attached test case Expected: We should get an error callback with INVALID_STATE. Actual: An error callback fires with "3" as the parameter. This is probably due to the fact that we're not providing the enumerated name here and instead, providing the numerical enumerated equivalent. I'm going to go ahead and guess there's probably other ways to reproduce this pretty easily with other error codes. Let's fire a "useful" error code back at the developer.
Reporter | ||
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•