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 21922 - components of a URL
Summary: components of a URL
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 enhancement
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-03 18:39 UTC by Marcos Caceres
Modified: 2014-05-22 14:24 UTC (History)
2 users (show)

See Also:

Attachments

Description Marcos Caceres 2013-05-03 18:39:00 UTC 
It would be nice if there was a <dfn> for the "URL components" that other specs could link to (in addition to being able to link to the individual components)
Comment 1 Anne 2013-05-04 08:33:05 UTC 
Could you provide some context?
Comment 2 Marcos Caceres 2013-05-04 12:43:02 UTC 
(In reply to comment #1)
> Could you provide some context?

In my own case [1], I have:

"The query and fragment components, when present, complement the path component in identifying a resource within a package. However, when dereferencing, the query and fragment components don't play any part in locating a file inside of package."

So, although I link to "query", "path", "fragment", it would be nice to also be able to link to "component". It's more for my own benefit, as I like to link and then check I haven't missed any. Hope that makes sense.    

[1] http://app-uri.sysapps.org/
Comment 3 Anne 2013-05-21 03:32:24 UTC 
I think when you actually define the dereferencing (as part of fetch or some such) you probably do not need that I think. Could discuss this next week.
Comment 4 Anne 2014-05-22 10:34:35 UTC 
Marcos, can this be WONTFIX?
Comment 5 Marcos Caceres 2014-05-22 14:24:36 UTC 
WONTFIX it is.