[Bug 13173] WF2: <input type="url"> should accept URLs with protocol omitted

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13173

Aryeh Gregor <Simetrical+w3cbug@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3
                 CC|                            |Simetrical+w3cbug@gmail.com
            Summary|<input type="url"> should   |WF2: <input type="url">
                   |accept URLs with protocol   |should accept URLs with
                   |omitted                     |protocol omitted
           Severity|normal                      |enhancement

--- Comment #1 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-07 17:28:03 UTC ---
The spec doesn't require particular UI for the new input types.  Browsers are
allowed to add protocols to user input if they want, as long as the value
visible to scripts and the value actually submitted are absolute URLs:

"""
User agents may allow the user to set the value to a string that is not a valid
absolute URL, but may also or instead automatically escape characters entered
by the user so that the value is always a valid absolute URL (even if that
isn't the actual value seen and edited by the user in the interface).
"""
http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#url-state

Here as in several other cases, it might be a good idea to suggest some ways
browsers might want to convert user input to a URL.  But the philosophy so far
has been that we don't want to *require* that browsers do specific
transformations on user input, if those transformations aren't visible to
script.

Bug 11579 is a similar idea.

-- 
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 Thursday, 7 July 2011 17:28:05 UTC