What should we do about onstatsended?

[henbos]

Now that there is little point to having track/sender/receiver stats dictionaries around because all their members are made obsolete (#479), it seems that the only use case for them are having objects that would trigger onstatsended.

So what is the use case for onstatsended? Well, it's nice to know if replaceTrack() was called so that you can correlate stats changing with that point in time.

I think we can do better and not mandate people implement track attachment stats anymore. So what do we do about onstatsended?

[henbos]

@vr000m

[vr000m]

We removed 'deleted' in #356 and #462 (leaving it here if earlier changes are impacted.)

[henbos]

TPAC decision: Remove "onstatsended" and file a separate issue for "onstatsevent" or "onreplacetrack" or what else to do.

[henbos]

Related TPAC decision: Remove "track" stats

[vr000m]

@pallab-gain @karthikbr82 @lennart-csio this may affect our implementation and use-cases, Please take a look and put together a proposal for alternate solutions (atm it seems to be about exposing an event on webrtc-pc)

[henbos]

onstatsended have now been removed from webrtc-pc: w3c/webrtc-pc#2305

[aboba]

@henbos Can we close this issue?

[henbos]

I think so, we know the path forward for now based on TPAC and suggestions for alternative events can be addressed separately