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

Issue 911265 link

Starred by 1 user
Status: Assigned
Owner:
bokan@chromium.org
Cc:
viswa.karala@chromium.org
█ suneel.k...@samsung.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

When you zoom in via touchscreen or touchpad, when you click on a section on a Wikipedia article, it is out of view

Reported by billdill...@gmail.com, Dec 3 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36

Example URL:

Steps to reproduce the problem:
Go to https://en.wikipedia.org/wiki/Google_Chrome . Now zoom in via touchscreen or touchpad. Next, tap or click on one of the sections in the "Contents" box (I chose "Speed" for the screenshot examples). Notice in Chrome, you don't see the "Speed" title, it brings you lower than it should. I did the same in Edge and did not have this problem. It seems like Chrome is not taking into account that the page has been zoomed in via touchscreen or touchpad

What is the expected behavior?

What went wrong?
I do not have access to a Mac or Chrome OS device to check, could someone check to see if this issue also applies to those platforms?

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 70.0.3538.110  Channel: stable
OS Version: 10.0
Flash Version:
chromezoom.png
360 KB View Download
edgezoom.png
379 KB View Download

Comment 1 by dtapu...@chromium.org, Dec 3

Components: Blink>Input

Comment 2 by swarnasree.mukkala@chromium.org, Dec 4

Labels: Needs-Triage-M70

Comment 3 by viswa.karala@chromium.org, Dec 4

Cc: suneel.k...@samsung.com viswa.karala@chromium.org
Components: Blink>Scroll
Labels: -Pri-2 -Type-Compat RegressedIn-69 Triaged-ET M-69 Target-70 Target-71 Target-72 Target-73 FoundIn-71 FoundIn-70 FoundIn-73 FoundIn-72 hasbisect Pri-1 Type-Bug-Regression
Owner: bokan@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on reported version 70.0.3538.110 and latest chrome# 73.0.3628.0 using Windows-10 surface pro, hence providing Bisect Info
Note: Unable to confirm the behavior of Linux and Mac, as ET doesn't have touch devices to test and confirm it.

Bisect Info:
================
Good build: 69.0.3466.0 
Bad build: 69.0.3472.0

On performig per-revision getting error, hence providing below change log from chromium bisect
You are probably looking for a change made after 569212 (known good), but no later than 569218 (first known bad).
Change Log: https://chromium.googlesource.com/chromium/src/+log/43bcd163e61c39aeebe2c72ea08037662442eb74..7d6721f24a5e330bb14212bf953f6e28b0c59fa2
Suspecting: https://chromium.googlesource.com/chromium/src/+/137ca58808d726e8f78727857a01f6b926034bf0 from above change log
Change-Id: I8357bcccbc88ffcd3b5d01265737a5b60f1e59a8
Reviewed-on: https://chromium-review.googlesource.com/1075956

Note: As the author(Suneel Kota) of the CL last visit is more than 30 days, hence assigning it to one of the reviewer(David Bokan)
@David Bokan: Please confirm the issue and help in re-assigning if it is not related to change.


Thanks!

Comment 4 by billdill...@gmail.com, Jan 7 

This might apply to other platforms too (Android, Chrome OS, macOS)
►

Sign in to add a comment