{"push_id":586550272,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ccf730e4b68ac5a36d39c027ccda740ed41d4645","before":"fac40298fbf23f4aea3a368142e1ae4ac6610393","commits":[{"sha":"ccf730e4b68ac5a36d39c027ccda740ed41d4645","author":{"email":"31fdf01f1d52fa46eb6a425a15c31b049f664f18@chromium.org","name":"alexmos@chromium.org"},"message":"Fix WebFrame::swap for remote FrameOwners.\n\nThis CL fixes two problems:\n\n1. In remote-to-local swaps for frames with a remote parent, the\nframe's FrameOwner will be a RemoteBridgeFrameOwner, and similarly to\nthe local owner case, it needs to get its content frame set to the new\nlocal frame.  This was exposed by load event forwarding introduced in\nhttps://codereview.chromium.org/937203003/, which made a few tests\ncrash on site isolation FYI bots, because they were trying to dispatch\na load event on a RemoteBridgeFrameOwner after a remote-to-local swap\nand crashing because RemoteBridgeFrameOwner::m_frame was null.\n\n2. \"localFrame.page()->setMainFrame(&localFrame);\"\nwas getting called when the owner() was not null and was remote.  It\nseems it should only be called when the owner() is null.  This was\ncausing a crash in blink::checkFrameCountConsistency in a new\nDynamicSandboxFlagsRemoteToLocal test I'm adding in\nhttps://codereview.chromium.org/891763004/.\n\nBUG=346764\n\nReview URL: https://codereview.chromium.org/957033004\n\ngit-svn-id: svn://svn.chromium.org/blink/trunk@190967 bbb929c8-8fbe-4397-9dbb-9b2b20218538","distinct":true,"url":"https://api.github.com/repos/dstockwell/blink/commits/ccf730e4b68ac5a36d39c027ccda740ed41d4645"}]}