Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebRTC names these events with ongathererstatechange vs just onstatechange because these all hang off a bigger peer connection object. ORTC however does not.
ongathererstatechange
onstatechange
This should change from:
partial interface RTCIceGatherer : RTCStatsProvider { attribute EventHandler? ongathererstatechange; }
To:
partial interface RTCIceGatherer : RTCStatsProvider { attribute EventHandler? onstatechange; }
The text was updated successfully, but these errors were encountered:
Sure.
Sorry, something went wrong.
Change:
partial interface RTCIceTransport : RTCStatsProvider { attribute EventHandler? onicestatechange; } partial interface RTCDtlsTransport : RTCStatsProvider { }
partial interface RTCIceTransport : RTCStatsProvider { attribute EventHandler? onstatechange; } partial interface RTCDtlsTransport : RTCStatsProvider { attribute EventHandler? onstatechange; }
ongathererstatechange vs onstatechange
a0a4a63
Fix for Issue #475
Yes, that PR fixes. Merged + closing.
No branches or pull requests
robin-raymond commentedApr 19, 2016
WebRTC names these events with
ongathererstatechange
vs justonstatechange
because these all hang off a bigger peer connection object. ORTC however does not.This should change from:
To:
The text was updated successfully, but these errors were encountered: