- From: <bugzilla@jessica.w3.org>
- Date: Wed, 30 Mar 2011 16:13:46 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12262 --- Comment #4 from Mounir Lamouri <mounir.lamouri@gmail.com> 2011-03-30 16:13:45 UTC --- (In reply to comment #3) > What happens if the displayed value doesn't match the value in .value? > > For example we've discussed adding a ", " to the end of the displayed value as > to make it easier to add additional email addresses, however since this would > result in an invalid address it wouldn't show up in .value or the submitted > string. > > Also, we might get fancy enough that we display the name along with the email > address if the browser gets access to an address book. In that case the name > would be displayed but not show up in .value. Good point. Then I don't know what we should do. I see a few possibilities: - Allow selection methods and attributes and expect implementations to be clever we .value isn't the shown value ; - Allow selection methods and attributes but also allow doing nothing if the widget is more complex than a simple text field ; - Not allowing selection methods and attributes because some implementation might be more complex than a simple text field (this is not the case currently AFAIK). -- 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 Wednesday, 30 March 2011 16:13:47 UTC