window.moveBy(x, y) changing Window Size when using small Values
Reported by
samum...@gmail.com,
Apr 24 2018
|
|||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36
Steps to reproduce the problem:
1. Create a Popup using something = window.open("yourweb.site", "something", "width=250,height=250,scrollbars=0")
2. Move the popup using something.moveBy(2, 2) in a setInterval
3. Watch the Popup
What is the expected behavior?
The Popup should move 2 pixels down and right every X ms.
What went wrong?
If the values in moveBy are small, the popup will grow instead of moving. When the values are 1, it will only grow, when the values are 2, it will grow about the same amout that it moves by.
Did this work before? N/A
Chrome version: 66.0.3359.117 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 21.0.0.213
PopupBlocker does not affect this behaviour.
,
Apr 24 2018
,
Apr 25 2018
Unable to reproduce this issue on reported version 66.0.3359.117 using Windows 7 with below steps. Navigated to http://leumasme.bplaced.net/HTMLTests.html and clicked on Start , observed popup moving but it didn't grow as shown in video. @Reporter: Could you please check the video and let us know if we miss anything. Please check the issue on fresh profile and let us know the behaviour. Any further info on reproducing the issue would help in further debugging. Thanks!
,
Apr 25 2018
Created new Profile, same thing. Using Windows 7. screen.availHeight == screen.height == 864 screen.availWidth == screen.width == 1536 Currently using Mainboard-Graphics "Intel(R) HD Graphics 2500 1.05GHz"as default for Chrome. Works like it should when using Internet Explorer with disabled Popup Blocker [Also using Mainboard Graphics].
,
Apr 25 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 25 2018
,
Apr 26 2018
Unable to reproduce this issue on windows 7 even on changing screen resolution. Attaching screencast and GPU details for further debugging of this from dev team. As issue is not reproducible for TE team removing Needs-Bisect label. Could someone from Blink>WindowDialog team please have a look at this issue. Thanks!
,
Apr 26 2018
Ah yeah right, gonna add the content of chrome://gpu here too. https://paste.ccbluex.net/?view=e5ae9cd21
,
May 2 2018
Re-tested this issue on Windows 7 on the latest Stable 66.0.3359.139 and Canary 68.0.3417.0 and unable to reproduce the issue. As this issue is not reproducible at TE end, adding 'TE-NeedsTriageHelp' label and requesting someone from Blink>WindowDialog team to look into this and help in further triaging. Thanks... |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by samum...@gmail.com
, Apr 24 2018