RTCTransportStats - updates #37158
RTCTransportStats - updates #37158
Conversation
Preview URLs (7 pages)
Flaws (10)Note! 6 documents with no flaws that don't need to be listed. 🎉 URL:
External URLs (1)URL:
(comment last updated: 2024-12-13 05:46:05) |
| - {{domxref("RTCTransportStats.iceLocalUsernameFragment", "iceLocalUsernameFragment")}} {{optional_inline}} {{experimental_inline}} | ||
| - : A string indicating the local username fragment that uniquely identifies the ICE interaction session managed by this transport. | ||
| This is the same value as the local {{domxref("RTCIceCandidate.usernameFragment")}}, and will change if the connection is renegotiated. |
There was a problem hiding this comment.
Note, the spec says
Set to the current value of the local username fragment used in message validation procedures [RFC5245] for this RTCIceTransport. It may be updated on
setLocalDescription()and on ICE restart.
it is not clear if that validation is something the browser does or the developer does (to me). I THINK that the fragment is used to associate the transport to the messages on it, so at this point the validation has already happened. i.e. that is of interest to browser developers, not end users.
I am not sure what a developer would do with this stat, though presumably they can map it to other stats that are part of the same session.
This updates
RTCTransportStatsto match BCD as part of mdn/mdn#384The properties match the set in BCD, but are not individually documented. This primarily creates those missing documents.