Closed
Bug 1102871
Opened 10 years ago
Closed 1 year ago
Using two screen setup, getUserMedia application test will recognize and will use the secondary screen only if it`s set up to be on the right side of primary screen.
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox35 | --- | wontfix |
firefox36 | --- | affected |
firefox37 | --- | affected |
firefox38 | --- | affected |
firefox-esr31 | --- | unaffected |
backlog | webrtc/webaudio+ |
People
(Reporter: bmaris, Unassigned)
References
Details
(Whiteboard: [webrtc-uplift])
Attachments
(1 file)
275.18 KB,
image/jpeg
|
Details |
STR:
1. Using a two screen setup, make the primary screen the one from right side - secondary screen on left side
2. Start Firefox.
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.
Expected results: Screens are properly displayed in Firefox output screen.
Actual results: Screens are reversed in output screen, and the content of the app can`t be seen.
Notes:
1. This issue can be reproduced only in Windows using Firefox 34 beta 11 and latest Nightly.
2. Screenshot showing the issue attached.
(TaskManager is the shared app, but it shown the area from same position in secondary screen)
Comment 1•10 years ago
|
||
It looks like this is causing us to share content that the user neither intended nor granted permission to share. Adding a needinfo to ensure you've actually seen this bug.
Flags: needinfo?(rjesup)
Comment 2•10 years ago
|
||
Yup. Hadn't noticed it; this appears to be sharing the correct area off the wrong screen.
Matt - are you available to fix this? I suspect it's just an "add offset for correct screen" bug. Otherwise jib, pkerr or I could take it.
Flags: needinfo?(rjesup) → needinfo?(linuxwolf)
Whiteboard: [webrtc-uplift]
Updated•10 years ago
|
status-firefox35:
--- → wontfix
status-firefox36:
--- → affected
status-firefox37:
--- → affected
status-firefox38:
--- → affected
status-firefox-esr31:
--- → unaffected
Comment 3•10 years ago
|
||
I believe Matt is working on other projects.
Randell-- Can you take this (at least for the initial investigation)? I'd like to know if this is an easy fix that we can uplift or if it's messier/more complicated). Since this has privacy implications, I'd love to have a fix by next week that hopefully we can uplift.
Assignee: nobody → rjesup
Flags: needinfo?(linuxwolf)
Priority: -- → P2
Target Milestone: --- → mozilla38
Comment 4•10 years ago
|
||
Moving to pkerr. Let's try to get multi-montior support in screensharing done in Q3.
Assignee: rjesup → pkerr
backlog: --- → webRTC+
Rank: 25
Target Milestone: mozilla38 → ---
Comment 5•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Updated•5 years ago
|
Component: WebRTC → WebRTC: Audio/Video
Comment 6•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:jib, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: paulrkerr → nobody
Flags: needinfo?(jib)
Updated•2 years ago
|
Severity: normal → S3
![]() |
||
Updated•1 year ago
|
Flags: needinfo?(jib)
Reporter | ||
Comment 7•1 year ago
|
||
Closing since this is not reproducible anymore using latest Firefox 123.0 build.
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
•