Regression:3 dot menu overlay is seen chopped in hangouts while exiting full screen. |
|||||||
Issue descriptionChrome Version: 57.0.2987.19 Dev OS: 14.04 Ubuntu,Windows What steps will reproduce the problem? (1)Sign in to chrome and go to https://hangouts.google.com/ >> Try video calling and select full screen from 3 dot menu. (2)Exit full screen from 3 dot menu and observe the overlay(Refer video) Expected Result:3 dot menu overlay should not be chopped after exiting full screen Actual screen:3 dot menu overlay is seen chopped after exiting full screen. This is a regression issue broken in M-57 Manual bisect Info: ================== 57.0.2956.0-Good Build 57.0.2957.0-Bad Build
,
Jan 31 2017
Bisect Info: =========== Good build : 57.0.2956.0, Revision Range- 439388 Bad build : 57.0.2957.0, Revision Range- 439663 After executing the per-revision-bisect script, i got the following CL's between good and bad build versions ============================================ https://chromium.googlesource.com/chromium/src/+log/a53b5cd4e3693faf88db6b2b953c515ab8db097c..19fa73af253fb8af1199767812814eb2c3f98295 The suspecting Change Log is : ----------- https://chromium.googlesource.com/angle/angle.git/+/a26c6b7ca90c4a3bc17f292f8b7aac3c06743a57 jmadill@- Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner. Thank You...
,
Jan 31 2017
Unable to reproduce in Canary on Windows. Need some help with this one.
,
Feb 2 2017
3 dot menu overlay should not be chopped after exiting full screen.Please find the attached files for Expected behaviour. jmadill@- Could you please look into the issue and let me know if anything required.
,
Feb 2 2017
,
Feb 2 2017
Unlikely to be ANGLE since you are on Linux, and ANGLE handles rendering on Windows. The shader translator is used on Linux but doesn't usually result in rendering errors. You'll need to find another owner. Unable to reproduce.
,
Feb 2 2017
cc'ing other ANGLE folks. I couldn't reproduce this on Windows.
,
Feb 2 2017
Please re-run the per-revision bisect. There's always the chance that with a manual bisect there might have been flaky behaviour at one step, or a slight mistake.
,
Feb 20 2017
Issue is not reproducible on latest M-57(57.0.2987.71)and M-58(58.0.3018.0) builds
,
Feb 20 2017
Closing the issue as per C#9, as the issue is not seen on the latest M-58 and M-57. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ajha@chromium.org
, Jan 31 2017Status: Untriaged (was: Unconfirmed)