0
Files
src/content/browser
Antonio Sartori ae8d3b4f81 Commit policy container to blink also on failed navigations
When implementing the policy container, we did not address the case of
failed navigations. At the moment, those navigations do not commit a
new PolicyContainer on the LocalFrame in blink (so the previous
PolicyContainer is kept), while they store the NavigationRequest's
PolicyContainerHost on the RenderFrameHost. This is clearly wrong,
since the LocalFrame's PolicyContainer is not paired up with the
RenderFrameHost's PolicyContainerHost anymore.

This CL fixes that by mimicking what we do for successful navigations:
we create a blink client for the NavigationRequest's
PolicyContainerHost which we send to blink alongside the
CommitFailedNavigation mojo message, and we use that to set the
LocalFrame's PolicyContainer.

Fixed: 1150834
Bug: 1130587,1150834
Change-Id: Ie326922274e87778e368438a9a7c213a94881ec6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2675241
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852302}
2021-02-09 19:36:54 +00:00
..
2021-01-12 22:25:18 +00:00
2021-01-26 01:27:16 +00:00
2021-02-02 01:47:13 +00:00
2021-02-04 23:25:06 +00:00