- From: <bugzilla@jessica.w3.org>
- Date: Sun, 10 Jul 2011 20:41:59 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13173 --- Comment #13 from Aryeh Gregor <Simetrical+w3cbug@gmail.com> 2011-07-10 20:41:58 UTC --- (In reply to comment #11) > One reason that comes to mind is showing accurate diagnostics to the user. More specifically? (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. Why do you want to use <input type=url>, if you want it to be able to contain things that aren't URLs? Something without a protocol is not a URL, and will not work in practically any scenario where a URL is needed -- e.g., <a href> or other types of links embedded in content. The only place where it will usually behave like a URL is if you type it into a navigation bar. -- 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 20:42:04 UTC