This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27528 - terminology: distinguish between URL objects and URL strings
Summary: terminology: distinguish between URL objects and URL strings
Status: RESOLVED DUPLICATE of bug 26405
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-05 22:32 UTC by Sam Ruby
Modified: 2014-12-06 14:22 UTC (History)
3 users (show)

See Also:


Attachments

Description Sam Ruby 2014-12-05 22:32:41 UTC
This bug is opened on behalf of Roy Fielding, based on http://lists.w3.org/Archives/Public/public-ietf-w3c/2014Dec/0007.html

Original comment:

I don't see any problem with continuing to use URL as the API name
for an object that contains a parsed reference and produces a URL string.
That should be distinguishable by context (e.g., code).  What I have
a problem with is the notion that both the input and the output of
those processes is a URL.  That is madness.  There is a reason why
the input is called href or src, not URL.
Comment 1 Anne 2014-12-06 14:22:58 UTC

*** This bug has been marked as a duplicate of bug 26405 ***