Philipp Hancke

Since echo detection is not perfect I think it should remain a likelihood, not a counter. How about the UA returning and indicator whether there was echo since the last...

This is mostly a consistency issue between the candidate object and the candidate stats, see [here](https://github.com/w3c/webrtc-stats/pull/611#issuecomment-1214673705) for details. I did consider (and actually implemented) .url as well but that is...

I think the following fiddle is forbidden https://jsfiddle.net/fippo/Lrdj4mwu/3/ yet passes https://www.rfc-editor.org/rfc/rfc8843#name-payload-type-pt-value-reuse says ``` all codecs associated with the payload type number MUST share an identical codec configuration. This means that...

seems we have a bug in multiple browsers, Firefox accepts the fiddle as well.

Matches the [polyfill I did](https://github.com/webrtcHacks/adapter/pull/1111), this should be useful

i'll eagerly await for your WPT then ;-)

what might contribute is that the safari shim is still wrapping the peerconnection constructor here: https://github.com/webrtcHacks/adapter/blob/master/src/js/safari/safari_shim.js#L235 @dagingaa any ideas?

https://datatracker.ietf.org/doc/html/rfc5389#section-15.11 - not something that can work even.

this mainly affects https://github.com/web-platform-tests/wpt/blob/master/webrtc-stats/supported-stats.html ?

More ref: https://source.chromium.org/chromium/chromium/src/+/main:media/capture/video_capture_types.h?q=googPowerLineFrequency%20 This used to be a nonstandard constraint in Chrome but that went AWOL