Closed
Bug 1102886
Opened 10 years ago
Closed 1 year ago
Wrong webrtc doorhanger pop-up placement using two screens setup.
Categories
(Core :: WebRTC, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
backlog | webrtc/webaudio+ |
People
(Reporter: bmaris, Unassigned)
References
Details
Attachments
(1 file)
104.32 KB,
image/jpeg
|
Details |
STR:
1. Using a two screen setup, start Firefox in secondary screen.
3. Navigate to about:config, search for 'media.getusermedia.screensharing.allowed_domains' and add 'people.mozilla.org' at the end.
4. Restart Firefox.
5. Navigate to https://people.mozilla.org/~fqueze2/webrtc/ff_gum_test.html
6. Click on Application button and share any given app.
7. Click on screen icon from global indicator.
Expected results: Doorhanger is opened and is correctly displayed in Firefox output screen (or is not displayed at all)
Actual results: Doorhanger is shown in the primary screen over the shared app.
Notes:
1. This is only reproducible on Windows. Not reproducible in Ubuntu 14.04 32bit (the doorhanger is not displayed in output screen)
2. Screenshot showing this issue attached.
Comment 1•10 years ago
|
||
Adding a needinfo just to ensure you have seen this bug. It seems the code drawing yellow rectangles over the covered areas of the shared application gets confused when there are several screens. In the attached screenshot we are obscuring an area we shouldn't, but I wonder if there's a risk of the opposite situation happening too.
Flags: needinfo?(rjesup)
Comment 2•10 years ago
|
||
yes, I've seen this. We'll try to find time to deal with RSN.
Flags: needinfo?(rjesup)
Updated•10 years ago
|
backlog: --- → webRTC+
Rank: 25
Priority: -- → P2
Comment 3•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
Reporter | ||
Comment 4•1 year ago
|
||
Closing since this is not reproducible anymore using latest Firefox 123.0 build and the global indicator is no longer present.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•