- From: <bugzilla@jessica.w3.org>
- Date: Wed, 16 Feb 2011 15:13:46 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12099 Summary: Input type=url: value range Product: HTML WG Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: stalinbulldog@gmail.com QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org As per the specification below, it appears that <input type='url' /> fields will not support the special form URL localhost, I believe this to be an oversight as in many cases when querying the user for a url, especially in the case of most post-form applications of this input type, localhost is a perfectly valid response. In example, a user is instructed to enter the information of a database to connect to, usually the response will be in the form of schema://<ipv4 addr> or localhost, however, occasionally it will take the form of a url [very likely one the user agent has encountered before]. Forcing this application to use the type='text' field will under-utilize the information the user-agent may be able to supply to the user. As an aside, thank you for your time in reviewing this. I am quite excited about the new introductions into the html standard this offers as it may help move web development away from reliance on obscure or arcane classes/ids. 4.10.7.1.4 URL state The value attribute, if specified, must have a value that is a valid URL potentially surrounded by spaces that is also an absolute URL 2.6 URLs A URL is an absolute URL if resolving it results in the same output regardless of what it is resolved relative to, and that output is not a failure. An absolute URL is a hierarchical URL if, when resolved and then parsed, there is a character immediately after the <scheme> component and it is a U+002F SOLIDUS character (/). An absolute URL is an authority-based URL if, when resolved and then parsed, there are two characters immediately after the <scheme> component and they are both U+002F SOLIDUS characters (//). To parse a URL url into its component parts, the user agent must use the parse an address algorithm defined by the IRI specification. [RFC3987] -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 16 February 2011 15:13:48 UTC