Open
Bug 1544107
Opened 7 years ago
Updated 1 year ago
createOffer/createAnswer fail to absorb JS state changes before resolving, violating spec.
Categories
(Core :: WebRTC: Signaling, defect, P3)
Core
WebRTC: Signaling
Tracking
()
REOPENED
People
(Reporter: jib, Unassigned)
References
Details
In the spec, the final steps to create an offer say:
"If connection was modified in such a way that additional inspection of the system state is necessary, or if its configured indentity provider is no longer provider, then in parallel begin the steps to create an offer again, given p, and abort these steps."
It appears we don't do that. STRs:
- Open https://jsfiddle.net/jib1/zL9njvq8/ and share camera + mic
Expected result:
negotiating
true
Actual result:
negotiating
false
negotiating
true
| Reporter | ||
Comment 1•7 years ago
|
||
Nevermind, comment 0 looks like pilot error on my part.
It seems our createOffer is mostly synchronous.
The only remaining issue here would seem to be bug 1171634.
Also, I'm wondering if this means we're firing the success callback too soon... Will open a new issue on that if that's the case.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 2•7 years ago
|
||
...and I still found a problem. I've updated the STRs.
Expected result:
negotiating
true
Actual result:
negotiating
false
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Priority: P2 → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•