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

Issue 684228 link

Starred by 2 users
Status: Duplicate
Merged: issue 491334
Owner:
kenrb@chromium.org
Closed: Feb 2017
Cc:
szager@chromium.org
wjmaclean@chromium.org
dtapu...@chromium.org
malteubl@google.com
skobes@chromium.org
bokan@chromium.org
█ nasko@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Can't scroll AMP pages with top document isolation enabled

Project Member Reported by esprehn@chromium.org, Jan 24 2017 
Chrome Version: 57.0.2987.4
OS: Android 7.1.1, Pixel XL

I've been seeing this for a week or so in canary.

What steps will reproduce the problem?
(1) Load https://www.google.com/amp/s/amp.cnn.com/cnn/2017/01/21/politics/womens-march-donald-trump-inauguration-sizes/index.html
(2) Try to scroll.

This works fine in stable.

Comment 1 by esprehn@chromium.org, Jan 24 2017

Owner: bokan@chromium.org
Status: Assigned (was: Untriaged)
bokan@ said he'd to look into this.

Comment 2 by bokan@chromium.org, Jan 24 2017 

I can't repro, I tried on Canary (58.0.2990.3) and Dev (57.0.2984.3) on Nexus 5X, Canary (57.0.2986.0) on Nexus 6 and Canary (58.0.2989.0) on a Samsung S7. Does this happen consistently or is it an intermittent issue?

Comment 3 by esprehn@chromium.org, Feb 5 2017 

I'm still seeing this. 58.0.3001.3

Comment 4 by esprehn@chromium.org, Feb 5 2017

Cc: dtapu...@chromium.org szager@chromium.org malteubl@google.com
 Issue 688769  has been merged into this issue.

Comment 5 by esprehn@chromium.org, Feb 5 2017 

I had to uninstall chrome Canary, it made all amp pages unusable on my pixel XL. :(

Comment 6 by bokan@chromium.org, Feb 6 2017 

Perhaps specific to the pixel XL, I'll try to track one down today.

Comment 7 by bokan@chromium.org, Feb 6 2017 

Tried on a Pixel XL in beta (57.0.2987.19) and canary (58.0.3001.3) but scrolling on AMP pages works fine, both the above link and random articles. Elliott, do you perhaps have some experimental flags enabled?

Comment 8 by esprehn@chromium.org, Feb 6 2017

Cc: nasko@chromium.org
Confirmed it's because of Top Document Isolation. I forgot I had it turned on in the flags.

Comment 9 by esprehn@chromium.org, Feb 6 2017

Summary: Can't scroll AMP pages with top document isolation enabled (was: Can't scroll AMP pages)

Comment 10 by nasko@chromium.org, Feb 6 2017

Cc: kenrb@chromium.org
Adding kenrb@, who has been looking at some scrolling issues recently.

Comment 11 by bokan@chromium.org, Feb 6 2017

Cc: -kenrb@chromium.org
Owner: kenrb@chromium.org
Assigning to Ken as it's an OOPIF issue. Happy to help if needed though.

Comment 12 by kenrb@chromium.org, Feb 6 2017

Cc: wjmaclean@chromium.org
Investigating.

Comment 13 by kenrb@chromium.org, Feb 6 2017 

Gah, for some reason I saw 'Pixel' and thought that this affected ChromeOS, forgetting about the name collision...

As an Android-only bug, OOPIF scrolling is known to be broken until I land this CL that adds browser-process hit testing: https://codereview.chromium.org/2509103002/

I don't consider OOPIF modes to be usable on Android until that happens.

However, it's not clear to me why main frame scrolling would be broken, and I am guessing it is some peculiarity about AMP. That might be worth poking at to see.

Comment 14 by bokan@chromium.org, Feb 6 2017 

AMP loads its content into a cross process iframe so that explains the OOPIF connection.

Comment 15 by kenrb@chromium.org, Feb 6 2017

Mergedinto: 491334
Status: Duplicate (was: Assigned)
Wow, thanks. In that case, this is entirely expected. I will follow up somewhere else on whether AMP is a known issue for TDI.

I have an OKR this quarter to bring OOPIF usability on Android up to its state on desktop. I started that work in November but have been dealing with a lot of bugs lately.
►

Sign in to add a comment