23573 2013-10-21 03:20:14 +0000 Drop maxlength="" and minlength="" on <input type=email> 2014-01-27 19:08:34 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/multipage/states-of-the-type-attribute.html#e-mail-state-(type=email) blocked waiting for data from Kent, per comment 2 P3 normal Needs Research 1 tkent ian annevk ayg ian jonas mathias mike mounir zcorpan contributor oldest_to_newest 94981 0 tkent 2013-10-21 03:20:14 +0000 Proposal: Remove maxlength/minlength attribute support for type=email * No good usecases. * Needs extra implementation cost because of IDN. * UAs can't show the detailed validation message for tooLong/tooShort Chrome and Firefox show the following message for type=text: > Please shorten this text to $MAX_CHARACTERS characters or less (you are currently using $CURRENT_LENGTH characters). Showing numbers like $MAX_CHARACTERS and $CURRENT_LENGTH for type=email is useless because of IDN, and UAs need to show an abstract message. 95049 1 ian 2013-10-21 21:38:34 +0000 Yeah, that's a good point. The original use case was servers that have a server-side limitation. What do you propose they do instead? Maybe I can include suitable advice in the spec for authors facing such limitations. 95328 2 tkent 2013-10-25 00:11:13 +0000 Yeah, it's possible that adding maxlength for a sever-side limitation. However I haven't seen actual instances of input[type=email][maxlength]. I'm afraid maxlength solves non-existent problem. Ok, I'll add usage-counting code of input[type=email][maxlength] to Google Chrome, and will report the result a few months later. I think minlength is really useless for type=email. 95374 3 ian 2013-10-25 23:26:12 +0000 It's true that I've never seen type=email maxlength... minlength is there purely because maxlength is. I didn't want there to be a one-off control that happened to only have one of the two or something. It seemed pointlessly complicated. Seems like a reasonable request. Anyone object? 95403 4 ayg 2013-10-27 12:03:06 +0000 Seems reasonable. 95410 5 mathias 2013-10-27 20:55:20 +0000 Removing it sounds good, but let’s wait for the data (comment #2) before making a decision. 95474 6 ian 2013-10-28 21:45:09 +0000 Roger. Kent, when you have the data please let us know, thanks! 99118 7 tkent 2014-01-27 01:55:22 +0000 It seems removing maxlength support for type=email is not reasonable. Google Chrome 32 Stable has usage counting code for type=email and maxlength. The result: Ratio of the number of input[type=email][maxlength]:not([multiple]) to the number of input[type=email]:not([multiple]) 23.8% Ratio of the number of input[type=email][maxlength][multiple] to the number of input[type=email][multiple] 0.4% FYI. Ratio of the number of input[type=email][multiple] to the number of input[type=email] 0.09% FYI. Ratio of the number of text inputs with maxlength to the number of text inputs 30.9% FYI. Ratio of the number of input[type=password][maxlength] to the number of input[type=password] 23.0% 99179 8 ian 2014-01-27 19:08:34 +0000 :-( I guess we'll mark this WONTFIX. :-(