[Webkit-unassigned] [Bug 104586] New: [chromium] Expose quickRedirectComing via WebDataSource

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=104586

           Summary: [chromium] Expose quickRedirectComing via
                    WebDataSource
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit API
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: creis at chromium.org
                CC: fishd at chromium.org


In Chromium, there are cases that the WebFrameClient needs to know whether the current navigation is a redirect that should replace the current history item.  This is kept in FrameLoader::quickRedirectComing().  We'd like to expose it via WebDataSource so that the client can use it in decidePolicyForNavigation.

Note that quickRedirectComing() is also exposed via DocumentLoader::isClientRedirect().  However, this isn't set until after decidePolicyForNavigation is called.  It's also confusingly named, since WebFrameClient::willPerformClientRedirect is called whether isClientRedirect() is true or not.  (willPerformClientRedirect refers to JavaScript navigations, whether they occur before or after the current document finishes loading, and thus it may sometimes leave the current history item in place.)

For reference, this is needed to fix http://crbug.com/164419.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.