[Webkit-unassigned] [Bug 165155] New: Web Inspector: parseURL should use URL constructor to better handle all kinds of URLs

[bugzilla-daemon at webkit.org]

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

            Bug ID: 165155
           Summary: Web Inspector: parseURL should use URL constructor to
                    better handle all kinds of URLs
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: All
                OS: All
            Status: NEW
          Keywords: DoNotImportToRadar
          Severity: Normal
          Priority: P2
         Component: Web Inspector
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: joepeck at webkit.org
                CC: bburg at apple.com, joepeck at webkit.org,
                    mattbaker at apple.com, nvasilyev at apple.com,
                    timothy at apple.com, webkit-bug-importer at group.apple.com

Summary:
parseURL should use URL constructor to better handle all kinds of URLs

Currently our parseURL URL Utility function returns an object with these properties: (in error cases they are null)

    scheme, host, port, path, queryString, fragment, lastPathComponent

The URL constructor, when passed without a base URL, returns an object with these properties: (in error cases this throws an exception)

    protocol, username, password, host, hostname, port, origin, pathname, search, hash (and searchParams special object)

We should convert over to using the URL constructor to avoid our own logic which may not (and does not always) match WebKit's URL parsing.

Notes:
- See LayoutTests/inspector/unit-tests/url-utilities.html for some examples

-- 
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/20161129/45b8d08b/attachment.html>