- From: <bugzilla@jessica.w3.org>
- Date: Tue, 19 Nov 2013 13:08:11 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=13154 --- Comment #30 from Cameron Jones <cmhjones@gmail.com> --- Okay, so for the type="range" input i agree that the approach you've just outlined is most prudent from the current requirements. The only further consideration i'd like is with regards to what future <input type="" multiple> might come up? If there are new type="" which may contain user text and allow multiple values, then my argument is that this would be better served by the client splitting these values prior to encoding so that a new microformat is not needed to deal with user escaping. Otherwise, if you think there will be no extensions requiring series encoding from <input>, then the concerns are largely moot. So, for example <input type="tel" multiple> would be a bad idea. OTOH, i think <select> has some great potential for collecting multiple values, but, of course, that can be looked at separately. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 19 November 2013 13:08:14 UTC