I agree about SF not affecting raw data - maybe it's worth having a "remove
training separator" option for multi-value fields in this case so form
authors can turn it on.
Sergey
On Tue, Apr 14, 2009 at 12:49 AM, Yaron Koren <[email protected]> wrote:
> Possibly... the problem is that I don't think Semantic Forms should be
> modifying user input - what the user types is considered, to some extent,
> "sacred" (as long as it passes validation). But is this really a problem? If
> #arraymap is used, the last comma shouldn't even appear on the page itself.
>
> -Yaron
>
>
>
> On Mon, Apr 13, 2009 at 2:23 PM, robertuva <[email protected]> wrote:
>
>>
>> This isn't a big issue, but from a usability perspective (and mostly
>> for those people that don't know how the system works) it would be
>> nice to remove the last comma and space on the last value of a field
>> that allows multiple values if it exists. This mostly becomes a
>> problem with autocomplete as it automatically adds the comma and space
>> there. If you don't manually remove it from the last value, then it
>> posts the value with that comma and space.
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Semantic Forms" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/semantic-forms?hl=en
-~----------~----~----~----~------~----~------~--~---
