New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 591370 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
(currently inactive on Chromium)
Closed: Mar 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

window.pageYOffset gives incorrect values when page zoomed on Chrome for Android

Reported by ol1...@gmail.com, Mar 2 2016

Issue description

Chrome Version       : 48.0.2564.95
URLs (if applicable) : google.com
 
Worked well on :
       Chrome v 44.*: OK

What steps will reproduce the problem?

1. Launch a website that is zoom enabled- for example: google.com on the latest version of Chrome on an Android mobile device version 5 or higher.
2. Zoom in the website whereas the viewport displays a scrolled position.
3. USB debug it using chrome on desktop with : chrome://inspect
4. Run window.pageYOffset or document.body.scrollTop in the console
5. scroll the page on the device and repeat step #4


What is the expected result?
Get the accurate offset of scroll Y position 

What happens instead?
Incorrect values - same result with different scroll positions.


Please provide any additional information below. Attach a screenshot if
possible.

 
JSchromeBug.JPG
107 KB View Download
JSChromeBug2.JPG
115 KB View Download
Labels: OS-Android
Cc: tedc...@chromium.org aelias@chromium.org
Owner: ymalik@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: bokan@chromium.org
Labels: Needs-Feedback
window.scroll properties were made relative to the layout viewport in M48. The reason you're seeing 0 is because the layout viewport is not scrolled. As a test, try scrolling to the bottom of the page, and this value should no longer be 0. 

This change was reverted in M49 (see  issue 571297 ). Can you verify that this is working in chrome beta?
Cc: ymalik@chromium.org
 Issue 591375  has been merged into this issue.
Can you also verify the same for getBoundingClientRect in  issue 591375 .

Comment 6 by ol1...@gmail.com, Mar 8 2016

First, thanks for the quick response. I just tested it on chrome beta and it is working well.
Regarding getBoundingClientRect in  issue 591375 , the issue still reproducing (and just noticed that it's status turned to won't fix) but at least for this I have a workaround. 
Status: Verified (was: Assigned)
Labels: Hotlist-Input-Dev

Sign in to add a comment