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

Issue 591375 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

getBoundingClientRect 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
 
Broken also on :
       Chrome v 44.*: FAIL

What steps will reproduce the problem?

1. Launch: google.com on the latest version of Chrome on an Android mobile device version 5 or higher.
2.  Zoom in (on the website) so that the viewport displays the page in a scrolled position.
3. USB debug, using chrome on desktop with: chrome://inspect tool
4. In console, run:
 > var el = document.getElementById('tmsb');
 > el.getBoundingClientRect().top;


What is the expected result?
Get the accurate element position in the viewport.

What happens instead?
Incorrect values - same result with different scroll positions (Attached).
 
chromeBug1.JPG
115 KB View Download
ChromeBug2.JPG
128 KB View Download
Labels: OS-Android
Cc: tedc...@chromium.org aelias@chromium.org
Owner: ymalik@chromium.org
Status: Assigned (was: Unconfirmed)
Mergedinto: 591370
Status: Duplicate (was: Assigned)

Comment 4 by bokan@chromium.org, Mar 7 2016

Status: WontFix (was: Duplicate)
This is actually not a dup. getBoundingClientRect has been returning values relative to the layout viewport since M41 and this is to match client coordinates in Mouse/Touch events. It wasn't changed as part of the inert visual viewport work and this is working as intended. IIRC, edge browser does the same thing here but I don't have a device to test on at the moment.

Sign in to add a comment