[Webkit-unassigned] [Bug 145969] New: [SOUP] Custom URI schemes don't work for requests containing a fragment identifier

[bugzilla-daemon at webkit.org]

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

            Bug ID: 145969
           Summary: [SOUP] Custom URI schemes don't work for requests
                    containing a fragment identifier
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Keywords: Gtk, Soup
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: cgarcia at igalia.com
        Depends on: 145968

For URIs like foo:bar#baz, what the custom protocol manager receives in the UI process is foo:bar, so the user can't handle fragments. Wrote a test case for GTK, see:

/webkit2/WebKitWebContext/uri-scheme: **
ERROR:../../Tools/TestWebKitAPI/Tests/WebKit2Gtk/TestWebKitWebContext.cpp:220:void testWebContextURIScheme(URISchemeTest*, gconstpointer): assertion failed (webkit_uri_scheme_request_get_uri(test->m_uriSchemeRequest.get()) == "echo:with#fragment"): ("echo:with" == "echo:with#fragment")

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150615/fe09f926/attachment.html>