Issue metadata
Sign in to add a comment
|
Chrome window moves down when loses focus
Reported by
hugef...@gmail.com,
Jun 2 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: This issue can be reproduced on some systems, not affecting each installation. See attachment which describes affected system. 0. Open browser and toggle its window to maximized state 1. Open any website (must contain <a> elements) 2. Click on Windows taskbar (Chrome will loose focus) 3. Move cursor to any <a> element without clicking 4. Chrome's window will move down by one pixel OS affected: Windows 10 x64 Note: I guess this problem is not affected only browsers, but some applications based on Blink (Slack, for example) is affected too (approved by me) What is the expected behavior? Main browser window must not move to any side when user moves cursor What went wrong? Main browser moves down and up when main window loses focus. Did this work before? Yes The first time when I reproduce this bug: Chrome 57 release date. Chrome version: 58.0.3029.110 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 25.0 r0 If user turns off 'Use hardware acceleration when available' option, the problem don't reproduce.
,
Jun 3 2017
Unfortunately I cannot provide any more information besides already provided. I can just guess that this problem is: 1) depends on videocard driver 2) depends on OS - I've reproduced this issue only on Win10 (https://drive.google.com/uc?id=0B3cugb5UBVPERkVtZnRDYlY4VlU), OS build version can be significant 3) Certainly depends on hardware acceleration state (must be turned on) This bug can be reproduced on latest Opera browser (It uses Blink too, you know) Or please tell me what you need to know when you asking for the testcase (I've already provided steps to reproduce)
,
Jun 3 2017
Thank you for providing more feedback. Adding requester "ligimole@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 3 2017
I've googled this problem and I found some workarounds: 1) Install any theme for browser 2) Disable hardware acceleration 3) Change scale to 100% (in windows screen settings, not browser) Thank you for quick response!
,
Jun 5 2017
Tested the issue on windows 10 using chrome M58 #58.0.3029.110 and M60 #60.0.3119.0 and followed below steps : 1. Launched chrome and opened amazon.com , that has different <a> elements. 2. Maximized the browser window and cliked on widnows taskbar and again focused the cursor to <a> element and didnt observe any browser move. Attached screencast for reference. @hugefast-- Could you please check attached screencast and confirm us if we had missed any steps in reproducing the issue and also please hep us by providing the screencast of the issue. Thanks!
,
Aug 1 2017
There is no valid updates happened in the last few months, closing the issue. Feel free to reopen if needed
,
Aug 1 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Jun 2 2017Labels: Needs-Triage-M58 Needs-Feedback Needs-Bisect