On Thu, 6 Jan 2011, Mounir Lamouri wrote: > > On Fri, 22 Oct 2010, Anne van Kesteren wrote: > >> I think it would be better to simply omit that trailing comma. Which > >> should be allowed. If the specification currently does not allow that > >> (somehow) it would be a bug and is just something that needs > >> clarification. > > > > Indeed. Also fixed. > > I don't see where/how this has been fixed. To me, it's clear that > "f...@bar.com, b...@bar.com" will now be represented as > "f...@bar.com,b...@bar.com" in the DOM but not "f...@bar.com, b...@bar.com," > (which will be "f...@bar.com,b...@bar.com,"). In addition, this value > seems to still be invalid. > > Can you point out the section/line that handle this case?
It was fixed by completely decoupling the /value/ from what the user edits. The user now edits /values/ (plural), and the user agent then "exports" the user's edits to the /value/. (Apologies for the similarity in the names of these concepts; it's difficult to come up with unique yet still understandable names that aren't too verbose.) This is defined in the part of the spec starting with "When the multiple attribute is specified on the element". -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'