New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 789298 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
█ alexclarke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Page.frameScheduledNavigation not called for HTTP redirects (302, 301)

Project Member Reported by dats@chromium.org, Nov 28 2017 
Chrome Version: ToT
OS: Linux

What steps will reproduce the problem?
(1) chrome --remote-debugging-port=9222
(2) chrome-remote-interface inspect:
(3)     Page.frameScheduledNavigation()
        Page.enable()
        Page.navigate({url:...})

What is the expected result?
Page.frameScheduledNavigation event fired with reason='httpHeaderRefresh'

What happens instead?
Event not fired.

Comment 1 by dats@chromium.org, Nov 29 2017

Cc: alexclarke@chromium.org
Status: Available (was: Untriaged)
From what I see it probably never worked for HTTP redirects. Event is hooked into DocumentLoader::CommitNavigation() based on content, which according to comment in URLRequestJob::NotifyHeadersComplete() is returned only after all HTTP redirects were followed. But I'm not familiar with the code, so maybe I'm wrong.

Comment 2 by pfeldman@chromium.org, Dec 11 2017

Status: WontFix (was: Available)
Please don't rely upon frameScheduledNavigation, it is likely to be deprecated and go away.

Comment 3 by alexclarke@chromium.org, Dec 11 2017 

Uhh please talk to us before you deprecated that.  It's vital for headless we have a functional replacement.
►

Sign in to add a comment