cef/libcef
Marshall Greenblatt d9efaee9b9 Fix routing of frame messages after cross-origin navigation (fixes issue #2849)
When navigating cross-origin a speculative RenderFrameHost (RFH) and
CefFrameHostImpl is created in the browser process for the new frame object
created in a new renderer process. The FrameAttached message then arrives for
the speculative RFH, and as a consequence interfaces are bound between the new
CefFrameHostImpl and the speculative RFH. If the pending navigation commits
then the existing RFH will be replaced with the previously speculative RFH.
Since interfaces are already bound we must keep the new CefFrameHostImpl. This
means that frame objects (including for the main frame) will now always change
after cross-origin navigation, and the old frame object will be invalidated.
2021-05-18 21:59:48 -04:00
..
browser Fix routing of frame messages after cross-origin navigation (fixes issue #2849) 2021-05-18 21:59:48 -04:00
common Convert legacy IPC messages to Mojo (fixes issue #3123) 2021-05-18 21:59:48 -04:00
features Create a ChromeBrowserHostImpl for every Chrome tab (see issue #2969) 2020-09-21 17:06:56 -04:00
renderer Convert legacy IPC messages to Mojo (fixes issue #3123) 2021-05-18 21:59:48 -04:00
resources Update to Chromium version 91.0.4472.0 (#870763) 2021-04-23 11:38:51 -04:00