[Webkit-unassigned] [Bug 47978] New: Relative URL resolution should use current frame's base URL

[bugzilla-daemon at webkit.org]

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

           Summary: Relative URL resolution should use current frame's
                    base URL
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: kling at webkit.org
                CC: abarth at webkit.org


When navigating through this test page:

http://www.timeterminal.se/qtwkbug/

The last page requested is "last.html" from a document with the URL /qtwkbug/bar/second.html
You'd expect it to open /qtwkbug/bar/last.html but it actually opens /qtwkbug/last.html

This appears to be a problem with relative URL resolution, Firefox and Chromium will use the calling document's base URL, Safari and QtWebKit use the outermost frame's base URL.

This behavior is caused by the following snippet in WebCore/bindings/generic/GenericBinding.h:

    // For historical reasons, we need to complete the URL using the
    // dynamic frame.
    Frame* frame = state->getFirstFrame();

If we change the getFirstFrame to getActiveFrame, we get the expected behavior.

There is probably indeed a reason we're doing this though, so I was hoping someone could shed some light on it.

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