This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11678 - <input type='email' multiple> should have the last comma stripped or being valid with a ending comma
Summary: <input type='email' multiple> should have the last comma stripped or being va...
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Blocks: 11137
  Show dependency treegraph
Reported: 2011-01-06 13:09 UTC by Mounir Lamouri
Modified: 2011-08-04 05:16 UTC (History)
5 users (show)

See Also:


Description Mounir Lamouri 2011-01-06 13:09:51 UTC
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.
Comment 1 Ian 'Hixie' Hickson 2011-02-08 00:18:04 UTC
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?
Comment 2 Ian 'Hixie' Hickson 2011-03-04 01:01:23 UTC
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:

Status: Rejected
Change Description: no spec change
Rationale: see comment 1
Comment 3 Michael[tm] Smith 2011-08-04 05:16:30 UTC
mass-move component to LC1