Open Bug 1615282 Opened 3 years ago Updated 8 months ago

Missing track ended event when closing a GetDisplayMedia shared window

Categories

(Core :: WebRTC: Audio/Video, defect, P2)

73 Branch
Unspecified
All
defect

Tracking

()

People

(Reporter: jan, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:73.0) Gecko/20100101 Firefox/73.0

Steps to reproduce:

When sharing a window using GetDisplayMedia the track ended event is missing if you close this window.

Sample:
https://jsfiddle.net/oe75yrmv/1/

In chrome the event is fired properly.

Tested in ff 72/73/74

Actual results:

track ended event is missing

Expected results:

track ended event should be signaled when closing the shared window.

Summary: Missing track ended event when closing an GetDisplayMedia sahred window → Missing track ended event when closing an GetDisplayMedia shared window
Summary: Missing track ended event when closing an GetDisplayMedia shared window → Missing track ended event when closing a GetDisplayMedia shared window

Filed https://github.com/w3c/mediacapture-screen-share/issues/136.

Leaving it as defect for now since Chrome does this.

Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Unspecified → All
Priority: -- → P2

Reproduced issue at Nightly 78. Neither closing captured screen or window nor executing stop() results in ended event being fired.

When stop() is executed ended attribute is set to true.

If the captured screen or window is simply closed track.readyState value is still "live" and track.muted value is false. How is that possible?

The spec issue in comment 1 has been closed, since the spec is already clear we should be firing the ended event here.

Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:jib, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jib)
You need to log in before you can comment on or make changes to this bug.