New issue
Advanced search Search tips

Issue 804504 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 914587



Sign in to add a comment

navigation initiator should be captured synchronously when the navigation is scheduled

Project Member Reported by caseq@chromium.org, Jan 22 2018

Issue description

We currently capture originator's location in LocalFrameClientImpl::DecidePolicyForNavigation(), which is commonly invoked asynchronously WRT to the code that initiated navigation, so it won't actually capture the stack.

https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/exported/LocalFrameClientImpl.cpp?rcl=6d47d4076e434c6b26e783563edd2ab48533e731&l=591

This needs to happen synchronously.
 
Blockedon: 914587

Sign in to add a comment