Closed
Bug 1322651
Opened 8 years ago
Closed 5 years ago
WebRTC screen sharing artifacts when sharing applications
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
RESOLVED
INVALID
People
(Reporter: serejkasimanovich, Unassigned)
Details
Attachments
(1 file)
404.30 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36 Steps to reproduce: Prerequisite: Windows 7 with Basic theme. 1. https://mozilla.github.io/webrtc-landing/gum_test.html 2. Share application (Windows Explorer, Skype) 3. Move other applications over one which shared. Actual results: There are artifacts on shared application. Expected results: Shared application should display correctly.
Reporter | ||
Updated•8 years ago
|
OS: Unspecified → Windows 7
Updated•8 years ago
|
Component: WebRTC → WebRTC: Audio/Video
Comment 1•8 years ago
|
||
Siarhei, is this 100% reproducible? Randell, do you know this code enough to reason about this? Will the 49 update affect this perhaps?
Flags: needinfo?(serejkasimanovich)
Flags: needinfo?(rjesup)
Reporter | ||
Comment 2•8 years ago
|
||
(In reply to Andreas Pehrson [:pehrsons] (Telenor) from comment #1) > Siarhei, is this 100% reproducible? > > Randell, do you know this code enough to reason about this? Will the 49 > update affect this perhaps? Yes
Updated•7 years ago
|
Flags: needinfo?(serejkasimanovich)
Comment 3•7 years ago
|
||
I manage to repro in Windows 10 with Nightly. I see that the application is visible only when it is in the foreground. Also it's visible the window layout of the other application currently running in a yellow color. The same with release version 51 of Firefox.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•7 years ago
|
Rank: 21
Priority: -- → P2
Comment 4•7 years ago
|
||
What Alex is seeing is the correct behavior - yellow NOTE: Application sharing on Windows and Linux will not show any data which is not visible to the user -- i.e. if the window is obscured it will show as yellow. If it's partially obscured, it will show as partially yellow. This is due to the APIs used to collect the data. I *thought* Window sharing worked the same way, but it doesn't, at least not on Win10. On a Win10 system running Nightly, I see exactly that behavior using https://mozilla.github.io/webrtc-landing/gum_test.html Note I'm using the default theme. Siarhei, does this reproduce using the default theme in Win7 or Win10? Also, what Graphics chipset/driver/version are you using?
Status: NEW → UNCONFIRMED
Rank: 21 → 17
Ever confirmed: false
Flags: needinfo?(rjesup) → needinfo?(serejkasimanovich)
OS: Windows 7 → Windows
Priority: P2 → P1
Summary: WebRTC screen sharing artefacts. → WebRTC screen sharing artifacts when sharing applications
Comment 5•7 years ago
|
||
Siarhei: Can you also provide more explicit details: can you try it with a smaller browser window, and move around a smaller application window? Does it work for some applications and not others? could you provide a image of it working, then move a window a bit and an image of how it failed in that case? Do you have one monitor or two? Have you tried Nightly? (https://nightly.mozilla.org/) Thanks! I'm unable to see any artifacts on Win10/Nightly.
Reporter | ||
Comment 6•7 years ago
|
||
Prerequisite: Windows 7 with Basic theme!!! 100% reproducible with a huge amount of applications.
Comment 7•7 years ago
|
||
Jesup, do you have a machine like that to test with?
Flags: needinfo?(serejkasimanovich) → needinfo?(rjesup)
Comment 8•7 years ago
|
||
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
Comment 9•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Comment 10•5 years ago
|
||
We no longer support the application capture backend. Closing as invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(rjesup)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•