Issue metadata
Sign in to add a comment
|
out of process iframes don't scroll chain |
||||||||||||||||||||||||
Issue descriptionChrome Version : 52.0.2725.0 OS Version: OS X 10.11.4 URLs (if applicable) : http://plexode.com/eval3/#s=aekVQXANJVQMbAx1KR1NCTkYBVFNEHj2PVVVRVBsQEEZPD1hKTEpRRkVKQg9QU0gQra8QMbdVQk0bJ0ZCVVZTskBEUE9VqlUEEJqzQhAnSk1GGytQSU9ALUZIqkVAQ1pANEJESVrgLkrATQ9LUUihHx0QlpiaD49J4dOQBPCgAaDDYBCQRhpRLIcfL7OQfAZeAAA= What steps will reproduce the problem? 1. Touchpad scroll over the wikipedia iframe until you hit the bottom. What is the expected result? The scroll should chain after you do a second scroll. What happens instead of that? The scroll never chains and you get stuck in the iframe. As best I can tell, this happens for all cross-origin iframes and has nothing to do with the content of the frame. This is working for me in Chrome 50 and doesn't work in Chrome 52. This is clearly a release blocker (scrolling gets stuck in nearly all ads on the web!), but I'm not sure when it was introduced. Will put M51 for now so we can be sure to verify it's not in M51. UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2725.0 Safari/537.36
,
May 16 2016
The top document isolation flag causes this behavior, for instance. Nobody has done the work to enable OOPIFs to chain scroll, as far as I know.
,
May 16 2016
M50 Stable is launching very soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged ASAP. All changes MUST be merged into the release branch by 5pm on May 20 to make into the desktop Stable final build cut. Thank you!
,
May 16 2016
Yeah this is working fine for me too - I'm guessing Ojan had some flag enabled. Removing RBS. Ojan, can you please confirm?
,
May 16 2016
Ugh. Sorry for the distraction. I did have TDI/OOPIF enabled.
,
May 16 2016
I think Ken as a fix for this on the way. Ken, what's the bug number?
,
May 16 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by tdres...@chromium.org
, May 16 2016