Re: [webrtc-extensions] Not clear what should happen if header extensions are inconsistent across bundled transports (#140)

It is an issue. Lets take this (only works in chrome canary with experimental web platform flags and uses the old semantics)
https://jsfiddle.net/fippo/o2rbhp4v/1/

It shows that the first transceiver still has all header extensions even though the video-timing one was removed.
It will not show up in the offer when it is removed from all transceivers.

Likewise, enabling a non-default extension for one transceiver shows them in all transceivers.
Last but not least disabling something supported by two transceivers of different kinds on one kind still shows up on the other: https://jsfiddle.net/fippo/o2rbhp4v/2/

I'd say we have an implementation bug here and it should not show extensions stopped for a particular transceiver.

-- 
GitHub Notification of comment by fippo
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/140#issuecomment-1410579896 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 31 January 2023 15:25:00 UTC