DevTools: fix Page.frameRequestedNavigation to report proper frame id when...
DevTools: fix Page.frameRequestedNavigation to report proper frame id when another frame is being navigated - Replace FrameLoadRequest::SetClientRedirect() with SetClientRedirectReason() that implies the request is for client redirect and provides the reason; - Move probe::frameRequestedNavigation to FrameLoader::StartNavigation() and as late there as possible, so we only fire it when we actually request browser to navigate; - Pass Frame* target_frame to probe::frameRequestedNavigation() and report target frame as frameId if present, so that when a frame requests another frame to navigate, the id of the latter is reported. Bug: b/130664370 Change-Id: Ia424542edc90d39977abf49335bb1a89345233a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1570424 Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Reviewed-by:Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#652240}
Showing
Please register or sign in to comment