• Florent Castelli's avatar
    Implement RTCRtpSender.setParameters() · 856e3eca
    Florent Castelli authored
    Only parameters encodings.active, encodings.maxBitrate and
    encodings.priority are effectively working and connected
    to the native layer.
    
    Due to discrepancies between the WebRTC specification and the
    native layers, the objects are not passed back from Javascript
    and converted to native directly, but instead the relevant fields
    are converted and patch the last result from getParameters().
    If any read-only field is implemented by the native layer but not
    exposed yet to Javascript, they will be left as is and won't cause
    any InvalidModificationError.
    
    Bug: 803494
    Change-Id: Ia59734e5c3eddb54e5a1448a04fdcefe5a41a279
    Reviewed-on: https://chromium-review.googlesource.com/969124Reviewed-by: default avatarStephen Chenney <schenney@chromium.org>
    Reviewed-by: default avatarHenrik Boström <hbos@chromium.org>
    Commit-Queue: Florent Castelli <orphis@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#551477}
    856e3eca
RTCRtpSender-setParameters-crash.html 1.43 KB