11678 2011-01-06 13:09:51 +0000 <input type='email' multiple> should have the last comma stripped or being valid with a ending comma 2011-08-04 05:16:30 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WONTFIX P2 normal --- 11137 1 mounir ian ayg ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 43854 0 mounir 2011-01-06 13:09:51 +0000 This is a follow-up from bug 11137. With bug 11137, we are making <input type='email' multiple>'s value easier to use because tokens have no longer leading or trailing whitespaces. However, there is still an issue when such a control is ended by a comma which can easily happen if there is a UI (with list or autocompletion for example). I think there are two solutions 1. Add a step 4 in "Whenever the user changes the element's values, the user agent must run the following steps:" which would consist of removing the last character if it's a comma; 2. Make such control valid if it's ending with a comma. The first solution seems better because the submitted value will be more simple to use because splitting on comma would not return a useless empty value at the end. But, for what I understand, with the latest change made on the specifications, it's still possible to directly change the value in the DOM and in the UI while the user is typing (it might be weird but that is an option). With such a change, it wouldn't be an option anymore. 45217 1 ian 2011-02-08 00:18:04 +0000 I don't really understand this. The change in bug 11137 was to make it more clearly the browser's responsibility to map the user's input to the underlying value. Why would the underlying value end with a comma now? 46264 2 ian 2011-03-04 01:01:23 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: see comment 1 53704 3 mike 2011-08-04 05:16:30 +0000 mass-move component to LC1