- From: <bugzilla@jessica.w3.org>
- Date: Thu, 06 Jan 2011 13:09:51 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11678
Summary: <input type='email' multiple> should have the last
comma stripped or being valid with a ending comma
Product: HTML WG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: mounir.lamouri@gmail.com
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
Blocks: 11137
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.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 6 January 2011 13:09:53 UTC