Chromium Code Reviews
DescriptionMixed content iframe checks should use top
Prior to this CL, we were using the parent frame when checking iframes for
mixed content. Unfortunately, that breaks the iTunes download page because it
uses an HTTPS iframe to kick off the HTTP download.
This CL causes us to use the top-level frame for this check. That's reasonable
because if the top-level frame is HTTP, the user doesn't have any expectation
that they're being protected from network attackers
This change effectively reverts https://src.chromium.org/viewvc/blink?revision=150260&view=revision. I tried partially reverting that revision by keeping the blocking behavior, but that broke a number of assumptions in Chromium about how didRunInsecureContent works. It also broke the ReferrerPolicyTest browser tests in worrying ways. I would like to get back to blocking mixed content iframes, but we'll need to do that without breaking the iTunes download page.
R=tsepez@chromium.org
BUG=244210
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=153937
Patch Set 1 #Patch Set 2 : Update expected results #Patch Set 3 : Drop back to canDisplay #Messages
Total messages: 20 (0 generated)
|