Open
Bug 1365353
Opened 8 years ago
Updated 3 years ago
Investigate using a JS Proxy for the PeerConnection shim that used in mochitests
Categories
(Core :: WebRTC, enhancement, P4)
Core
WebRTC
Tracking
()
NEW
People
(Reporter: ng, Assigned: ng)
Details
A JS Proxy[0] implementation of the PeerConnection shim used in the mochitests could prove to be a significant code reduction and simplification. All methods that do not need to specifically overriden could be generically logged or counted as necessary then transparently proxied back to the underlying PeerConnection. This would reduce the amount of work that needs to be done on the shim to 0 for changes to the PeerConnection API that do not require special handling.
[0] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy
|
Assignee | |
Updated•8 years ago
|
Rank: 35
|
||
Comment 1•8 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•