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

Issue 613137 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Feature



Sign in to add a comment

Cannot zoom in/out in "Request Desktop Site" mode in Chrome(Mobile)

Reported by somcs...@gmail.com, May 19 2016

Issue description

Steps to reproduce the problem:
1. Open Chrome Browser in any mobile devices
2. Enter "smt.docomo.ne.jp"
3. Enable "Request Desktop Site" from browser option

What is the expected behavior?
Site should be able navigate in all directions

What went wrong?
Unable to slide horizontally, but the site is loaded completely.
Enabling "force zoom" from settings option allows the site to be navigable.

Did this work before? N/A 

Chrome version: Chrome Version: 50.0.2661.89   Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
 
chromemay19.txt
716 KB View Download
Cc: bokan@chromium.org jdduke@chromium.org
Components: Blink>Scroll
Status: Available (was: Unconfirmed)
This issue is reproducible, tested on Nexus5/6.0.1. 

Logs @ http://go/chrome-androidlogs1/6/613137

Comment 2 by bokan@chromium.org, Jun 9 2016

Cc: -jdduke@chromium.org aelias@chromium.org
Components: -UI -Blink>Scroll Blink>Input
Labels: -Type-Bug -Pri-2 Pri-3 Type-Feature
The page has a viewport <meta> tag that explicitly disables zooming so we're technically doing the right thing in this case.

Perhaps in RDS we should ignore reading meta tags like a desktop browser would? Off hand, I can't think of any obvious way that would break things and would improve the experience on desktop pages like this that just cargo-cult viewport meta tags because they don't affect desktops. +aelias, WDYT?
Status: Fixed (was: Available)
> Perhaps in RDS we should ignore reading meta tags like a desktop browser would?

Done already and you lgtm'ed the patch: https://codereview.chromium.org/1785953002/ .  This issue no longer reproes on 53.0.2757.2.

Comment 4 by bokan@chromium.org, Jun 9 2016

Doh! I remembered some recent changes here but forgot what they were :P

Sign in to add a comment