Bug 1975032 Comment 9 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Byron Campen [:bwc] from comment #8)
> We aren't populating the sequence number because we aren't being supplied with one by libwebrtc:

The docs do have the comment "and no `sequenceNumber` because this is an outgoing frame.", so perhaps this is expected.
Revision 1 by
on 
(In reply to Byron Campen [:bwc] from comment #8)
> We aren't populating the sequence number because we aren't being supplied with one by libwebrtc:

The docs do have the comment "and no `sequenceNumber` because this is an outgoing frame.", so perhaps this is expected.

The ordinary tests also show receiveTime on Chrome which doesn't show up in the fiddle.
Revision 2 by
on 
(In reply to Byron Campen [:bwc] from comment #8)
> We aren't populating the sequence number because we aren't being supplied with one by libwebrtc:

The docs do have the comment "and no `sequenceNumber` because this is an outgoing frame.", so perhaps this is expected.

The ordinary tests also show receiveTime on Chrome which doesn't show up in the fiddle (by which I mean I ran the wpt tests and stopped them at a point I could inspect chrome results.)
Revision 3 by
on 
(In reply to Byron Campen [:bwc] from comment #8)
> We aren't populating the sequence number because we aren't being supplied with one by libwebrtc:

The docs do have the comment "and no `sequenceNumber` because this is an outgoing frame.", - also in spec "The RTP sequence number as defined in [RFC3550]. Only exists for incoming audio frames."

The ordinary tests also show receiveTime on Chrome which doesn't show up in the fiddle (by which I mean I ran the wpt tests and stopped them at a point I could inspect chrome results.)
Revision 4 by
on 
(In reply to Byron Campen [:bwc] from comment #8)
> We aren't populating the sequence number because we aren't being supplied with one by libwebrtc:

The docs do have the comment "and no `sequenceNumber` because this is an outgoing frame.", - also in spec "The RTP sequence number as defined in [RFC3550]. Only exists for incoming audio frames."

The ordinary tests also show receiveTime on Chrome which doesn't show up in the fiddle (by which I mean I ran the wpt tests and stopped them at a point I could inspect chrome results.)

I'd love to verify that with a test if you have one.

Back to Bug 1975032 Comment 9