New issue
Advanced search Search tips

Issue 612260 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature



Sign in to add a comment

Don't rely on the presence of pending_navigation_params_ to distinguish between browser- and renderer-initiated navigations

Project Member Reported by a...@chromium.org, May 16 2016

Issue description

 Bug 597239  was due to the assumption that having pending navigation parameters meant that the current navigation was browser-initiated. We fixed it by piping in the value from Blink.

There are several other places where that assumption is made, and we should probably switch those places over to doing something similar.
 

Comment 1 by a...@chromium.org, May 19 2016

Cc: a...@chromium.org
Owner: ----
Status: Available (was: Assigned)
I was working on https://codereview.chromium.org/1983913002/ and got to the point where it seems like there is no good solution that solves everything. We might want to do this, but it'll involve more work in Blink than I currently have the expertise to do.
Project Member

Comment 2 by sheriffbot@chromium.org, May 22 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment