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 14935 - An absolute URI not IRI
Summary: An absolute URI not IRI
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-25 15:13 UTC by contributor
Modified: 2012-07-18 18:41 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2011-11-25 15:13:41 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-input-element.html
Multipage: http://www.whatwg.org/C#attr-input-type-keywords
Complete: http://www.whatwg.org/c#attr-input-type-keywords

Comment:
An absolute URI  not IRI

Posted from: 83.103.74.23
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0
Comment 1 Ian 'Hixie' Hickson 2011-12-07 23:31:26 UTC 
It's technically an absolute URL as defined in the spec, but at a high level that's equivalent to an absolute IRI, which is why I used that term in the non-normative table... but I guess that confuses more than clarifies, so I'll just change it to "absolute URL" without xreffing it.
Comment 2 contributor 2012-01-31 20:26:20 UTC 
Checked in as WHATWG revision r6951.
Check-in comment: Try to make things clearer.
http://html5.org/tools/web-apps-tracker?from=6950&to=6951