Open Bug 1325108 Opened 8 years ago Updated 2 years ago

Closing window (application) will continue to display latest preview in the sharing area

Categories

(Core :: WebRTC, defect, P3)

defect

Tracking

()

Tracking Status
firefox-esr45 --- wontfix
firefox50 --- affected
firefox51 --- affected
firefox52 --- wontfix
firefox53 --- affected

People

(Reporter: JuliaC, Unassigned)

References

(Blocks 1 open bug, )

Details

[Affected versions]: - latest Nightly 53.0a1 (2016-12-19) - latest Aurora 52.0a2 (2016-12-19) - 51.0b9 (20161219140923) - 50.1.0 (20161208153507) [Affected platforms]: - Mac OS X 10.12.1 - Ubuntu 14.04 x86 - Windows 10 x64 [Steps to reproduce]: 1. Lanuch Firefox 2. Navigate to about:config and confirm that: * media.getusermedia.screensharing.allow_on_old_platforms is false; * media.getusermedia.screensharing.enabled is true * media.getusermedia.screensharing.allowed_domains is set to many different websites, including mozilla.github.io 3. Go to https://mozilla.github.io/webrtc-landing/gum_test.html - have al least one more open applications 4. Click the Application button (or the Window button) 5. Choose the desired application from the "Application to share" drop down (or the desired window from the "Window to share" drop down) 6. Click the "Share selected Application" button (or the "Share selected Window" button) - inspect the sharing area 7. Close the application / window chosen in step 5 - inspect the sharing area [Expected result]: - Once closed, the chosen application / window is not shared anymore [Actual result]: - Even after is closed, the latest preview of the chosen application / window is still displayed in the sharing area [Regression range]: - This issue is not a recent regression, as is reproducible all the way back to Firefox 42 [Additional notes]: - Only the Window case is reproducible on Ubuntu and Windows platforms
Rank: 25
Priority: -- → P2
Normally, all window and app captures "freeze" when the source goes away. This is basically a side-effect of that - no new frames are generated. If we believe this is really objectionable, we could insert a black frame, or notice that the track has ended in the UI code.
Mass wontfix for bugs affecting firefox 52.
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.