Closed
Bug 847180
Opened 11 years ago
Closed 11 years ago
Requesting gUM concurrent access across multiple tabs - the sharing icon does not show on one tab until clicked explicitly
Categories
(Firefox :: Site Permissions, defect)
Firefox
Site Permissions
Tracking
()
RESOLVED
DUPLICATE
of bug 825723
Tracking | Status | |
---|---|---|
firefox20 | --- | unaffected |
firefox21 | --- | unaffected |
firefox22 | --- | affected |
People
(Reporter: jsmith, Unassigned)
Details
(Keywords: regression)
Steps: 1. Go to http://mozilla.github.com/webrtc-landing/gum_test.html in tab #1 in window #1 2. Select Video 3. Accept perms 4. Go to http://mozilla.github.com/webrtc-landing/gum_test.html in tab #2 in window #2 5. Select Video 6. Accept perms Expected: The sharing dialog should show on both tabs - green icon, indicating your camera is being shared. Actual: See http://i.imgur.com/HPECKnc.jpg. The sharing icon appears to be missing one of the windows (3/4 is cut off). If you click it, then the sharing icon appears.
Reporter | ||
Updated•11 years ago
|
Blocks: getUserMediaUI, 843971
Whiteboard: [getUserMedia][blocking-gum+]
Reporter | ||
Updated•11 years ago
|
Keywords: regression
Reporter | ||
Comment 1•11 years ago
|
||
In order to uplift bug 843971 safely, we will need to fix this followup regression. We haven't uplifted the bugs just yet, so FF 20 and FF 21 are unaffected by this regression. But noming for tracking as this is a blocking regression and needed to be fixed to safely uplift bug 843971 to Beta.
status-firefox20:
--- → unaffected
status-firefox21:
--- → unaffected
status-firefox22:
--- → affected
tracking-firefox20:
--- → ?
tracking-firefox21:
--- → ?
tracking-firefox22:
--- → ?
Comment 2•11 years ago
|
||
-> Dao as I believe this clearly is a UI/display issue. I also see the ">" instead of #> (where # is the green camera icon). Also, I'll note this only applies to sharing the camera across windows - within the same window (different tabs) the problem doesn't (can't really) occur. So there's an indication there, but for some reason it's not fully visible in the "share across two windows case". It also collapses when you Stop capturing in the other window, but restores if you focus the window. I'm not certain this would rise the level of blocking as the indicator is there (though partly obscured), and focusing the window in any way restores it (and leaves it restored), and it still shows up in the always-visible-in-every-window dropdown. So it only would be an issue if you have two fully (or largely) visible windows, you share the camera/mic in both of them, and then depend on the non-focused-window's URL-bar indicator to know if it's capturing. This is definitely a bug, and one that touches on privacy, but it's not a total failure to inform the user they're being captured, so this may deserve a judgement call from release-drivers and privacy - assuming we can't trivially fix it ASAP, which I strongly hope we can.
Assignee: nobody → dao
Priority: -- → P1
Reporter | ||
Comment 3•11 years ago
|
||
Putting blocking back into question and also putting needs info on Monica to see if she what thinks about comment 2.
tracking-firefox20:
? → ---
tracking-firefox21:
? → ---
tracking-firefox22:
? → ---
Flags: needinfo?(mmc)
Whiteboard: [getUserMedia][blocking-gum+] → [getUserMedia][blocking-gum?]
Comment 4•11 years ago
|
||
Pretty sure this is bug 825723.
Comment 5•11 years ago
|
||
We probably should dup this against bug 825723, or at least make it dependent on it. Also, this makes me wonder if this was just noticed and has always been there, or if changes to how we put up/refresh the notification exposed bug 825723.
Reporter | ||
Comment 6•11 years ago
|
||
Looking at Jared's screenshot, this definitely looks like a dupe of bug 825723. Good news is this is consistent STR, so this should help in fixing bug 825723.
Assignee: dao → nobody
No longer blocks: getUserMediaUI, 843971
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(mmc)
Priority: P1 → --
Resolution: --- → DUPLICATE
Whiteboard: [getUserMedia][blocking-gum?]
Updated•9 years ago
|
Component: General → Device Permissions
You need to log in
before you can comment on or make changes to this bug.
Description
•