We plumb the post transform rect to the child renderer which in turn uses that rect to compute the size of the CompositorFrame. The size of the content area does not change. This results in clipping of content in the OOPIF.
This bug requires manual review: Request affecting a post-stable build
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), abdulsyed@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Can you please comment on which OS this impacts? (My guess is desktop (Windows, mac, linux))
This also seems like a fairly large change. Can you please comment on why this is absolutely critical for M64 vs waiting until M65? I believe this was discussed on Tuesday's sync, but since the fix seems quite complex, my recommendation is to wait until M65.
r533403 landed in 66.0.3336.0, and I can verify the fix in Windows Canary 66.0.3340.0 with a https://googlesyndication.com subframe process (using https://clawr.users.x20web.corp.google.com/www/b/71913328/container-local.html). For comparison, I do see the bug in 65.0.3325.31 and 64.0.3282.140.
Per Abdul's comment in http://b/71913328#comment46, it seems like we should target M65 for this instead, unless we hear otherwise about the urgency.
Fady, can you comment on the safety of the change for the M65 branch? Is it risky to merge there, or do you expect it be safe? Thanks!
Your change meets the bar and is auto-approved for M65. Please go ahead and merge the CL to branch 3325 manually. Please contact milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by fsam...@chromium.org
, Jan 29 2018