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

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

From: <bugzilla@jessica.w3.org>
Date: Sun, 10 Jul 2011 21:01:42 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qg18I-0004A2-Oi@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13173

--- Comment #16 from Marat Tanalin <mtanalin@yandex.ru> 2011-07-10 21:01:42 UTC ---
(In reply to comment #13)
> (In reply to comment #11)
> > One reason that comes to mind is showing accurate diagnostics to the user.
> 
> More specifically?

See comment 14.

> (In reply to comment #12)
> > Quoting myself: "To have full control of input data". In development, full
> > control is always preferable over partial control when something is unknown.
> > Full control provides more flexibility regardless of a specific case.
> 
> <input type=text> gives full control.

Thats why I'm currenly ignoring <input type="url"> completely.

> Why do you want to use <input type=url>,
> if you want it to be able to contain things that aren't URLs?

There is big difference between any arbitrary string and URL with just protocol
omitted and assumed to be most widely used "http://" one. HTTP protocol is
default in most cases (for example, most websites has HTTP protocol like
http://example.com/, not HTTPS or, say, FTP).

> The only place where it will usually behave like a URL is if you type
> it into a navigation bar.

URL entered by user is not to _behave_ like a URL. It is just input string that
comforms to certain format.

By the way, to make it easier for client-side scripting to get full URL (with
protocol included regardless of whether it is entered by user), there may be a
special JavaScript method of the <input type="url"> element--for example,
getNormalizedUrl() or getFullUrl() (this is much different from and better than
situation when browser is transforming input.value itself).

-- 
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 Sunday, 10 July 2011 21:01:44 UTC

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