W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 17 Aug 2011 04:01:55 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QtXKF-000125-9L@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13173

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX
  Status Whiteboard|Hixie: see comment 1,       |
                   |comment 7                   |

--- Comment #22 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-08-17 04:01:53 UTC ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: 

<input type="url"> can already accept URLs with protocol omitted, it's up to
the UA.

A UA can in fact use whatever UI it wants here. It could have a UI consisting
of a large full-screen selection of the user's three most-visited sites, and
only allow the user to select one of those three sites' URLs, without the user
ever seeing the URL, only ever seeing screenshots of those sites. It could
require that the site dictate the URL character by character. It could prevent
the user from giving http:// URLs altogether, always forcing the domain and
path given by the user to be prefixed by https://. It could provide a
complicated multi-segment editor where you get to select the scheme by
drop-down, then type in the domain, then select the port using a spinner
control. It could allow you to select the URL only by asking you to type in
keywords which it then uses to perform Bing searches from which it uses the URL
of the first result. It could require you to mime the description of the page
whose URL you want to give. It could display pretty icons for the scheme and
not show it at all.

If you want something different  for example, if you want the browser to just
send to the server the exact string that the user typed  then you should not
use type=url, you should use type=text.

Note that nothing requires that the UA show to the user that it is
automatically prefixing an incomplete URL with "http://". Indeed, nothing
requires that the UA show the URL to the user at all. The UA could just always
show "http://foo.example.com/" and never show the user's input to the user,
instead requiring the user to type blindly.

-- 
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, 17 August 2011 04:02:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:17 UTC