Sometimes preview section slightly shifts towards right show a thin black strip on the left when application is moved to background
Reported by
sunilkum...@gmail.com,
Apr 7 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Chrome application developed using WebRTC to share the app screen and app contents 2. when ever app content shared with other person ,the shred content sifted to right side giving some margin on webRTC. 3. This happens when rendering happens through webRTC What is the expected behavior? You can take example of Google Hangout.when video rendering happens through webRTC,the rendering portion shifts to the right.Which should be centrally to the screen. What went wrong? Which effects in dark black line in left of the video rendering screen. Thais is a issue occurs only on some window 7 chrome browser with webRTC when rendering done by webRTC. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? No Chrome version: 47.0.2564.116 Chrome version: 48.0.2564.116 Channel: n/a OS Version: OS X 10.10.5 Flash Version: Shockwave Flash 21.0 r0
,
Apr 14 2016
Follow up questions for sunil@: a) Please provide screenshot(s) that show the problem. b) "Thais is a issue occurs only on some window 7 chrome browser with webRTC when rendering done by webRTC." Can you confirm that this is a Windows issue? I ask because the UserAgent info at the top of your report and OS info at the bottom indicate you used a Mac when filing this bug. c) "Does this work in other browsers? No Chrome version: 47.0.2564.116" Does this mean you were using Chrome 47.0.2564.116 on the Windows 7 machines where you saw this bug? If so, please update Chrome on those machines, as Chrome 47 is quite old. For comparison, Chrome 49 went to the stable channel on March 2, 2016 [1], and Chrome 50 was actually just released to the stable channel yesterday [2]. It would be best if you could update to Chrome 50 and report back your results. [1] http://googlechromereleases.blogspot.com/2016/03/stable-channel-update.html [2] http://googlechromereleases.blogspot.com/2016/04/stable-channel-update_13.html
,
Apr 28 2016
It's been 2 weeks since we requested feedback from the original reporter, and I haven't seen a follow up response. Closing as wontfix.
,
Sep 29 2016
|
||||
►
Sign in to add a comment |
||||
Comment 1 by keishi@chromium.org
, Apr 14 2016