[Webkit-unassigned] [Bug 142095] New: Declaring a custom protocol for "http" causes navigation issues

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Feb 27 11:53:33 PST 2015


            Bug ID: 142095
           Summary: Declaring a custom protocol for "http" causes
                    navigation issues
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: redswill at gmail.com

Created attachment 247532
  --> https://bugs.webkit.org/attachment.cgi?id=247532&action=review
Sample Project

Registering a custom protocol for "http" causes navigation issues, even if the protocol does nothing (i.e. it always returns NO in canInitWithRequest:)

Steps to reproduce:
1. Open & run the attached sample project
2. Search Google for "getbootstrap"
3. Click on the result that takes you to getbootstrap.com
4. Notice how the page fails to load
5. Right click and show inspector, then go to errors
6. Notice how WebKit tries to load the getbootstrap.com resources from google.com

Basically, the custom protocol somehow causes WebKit to get confused about what its current URL is and how to resolve relative paths.

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

More information about the webkit-unassigned mailing list