28356 2015-03-27 23:43:59 +0000 Why was the multiple attribute chosen as a ‘must not be specified’ in this spec? 2015-03-30 23:23:25 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED NEEDSINFO https://html.spec.whatwg.org/#text-(type=text)-state-and-search-state-(type=search) P3 normal Unsorted 1 contributor ian ian john mike contributor oldest_to_newest 118997 0 contributor 2015-03-27 23:43:59 +0000 Specification: https://html.spec.whatwg.org/multipage/forms.html Multipage: https://html.spec.whatwg.org/multipage/#text-(type=text)-state-and-search-state-(type=search) Complete: https://html.spec.whatwg.org/#text-(type=text)-state-and-search-state-(type=search) Referrer: Comment: Why was the multiple attribute chosen as a ‘must not be specified’ in this spec? Reason I query it, was hoping to gives users the ability to autocomplete nicknames/handles to reference others without needing to dip into javascript, and this pattern that already exists for input[type=file], input[type=email] seems obviously reusable. Browsers like Chrome validate datalists for email, so automatically reject content such as "@user" It is fairly common, with examples such as Twitter, Twitch chat, Web IM, and most collab tools, to highlight user(s) by name with tab completion. -jdw Posted from: 84.92.108.8 User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/40.0.2214.111 Chrome/40.0.2214.111 Safari/537.36 118998 1 john 2015-03-27 23:46:25 +0000 I was the reporter, CCing. 118999 2 john 2015-03-28 00:12:22 +0000 Found an issue that was WONTFIXd on Chromium, due to Spec https://code.google.com/p/chromium/issues/detail?id=225336 119109 3 ian 2015-03-30 23:23:25 +0000 It's not clear how you'd implement this. Multiple values in the form data set? What would the UI look like? Isn't this just a <textarea> with multiple lines of input basically?