[
https://issues.jboss.org/browse/RF-12664?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč commented on RF-12664:
---------------------------------
This behavior was introduced with RF-12445 and it is expected.
The description of new behavior is here:
https://github.com/richfaces/components/blob/develop/input/ui/src/main/ja...
The introduction of this behavior avoids need to define space as token character to use it
as separators.
The space character is used as in {{trim()}} function, e.g.:
{code}
token: ","
input: "Washington, Colorado,North Carolina"
output: [ "Washington", "Colorado", "North Carolina" ]
token: ",; "
input: "Vancouver, Maple Leafs; Toronto"
output: [ "Vancouver", "Maple", "Leafs", "Toronto"
]
{code}
Showcase - rich:autocomplete - space separator works even when token
is set just to comma
-----------------------------------------------------------------------------------------
Key: RF-12664
URL:
https://issues.jboss.org/browse/RF-12664
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-input, showcase
Affects Versions: 4.3.0.M3
Environment: Chrome 23 and FF 17
JBoss AS 7.1.1.Final
Reporter: Juraj Húska
Fix For: 4.3.0.CR1
Original Estimate: 1 hour
Remaining Estimate: 1 hour
It works to fill in values in to the autocomplete input separated with spaces, even
though the {{token}} attribute is set just to the comma separator.
I tried this behavior when I saw
[
this|https://github.com/richfaces/showcase/commit/ad703a86ef29a6b41146a9b...]
commit merged with upstream and it worked that time. I do not know why it is not working
for me with 4.3.M3 release. I tried it also with 4.3.0-SNAPSHOT and the issue is also
there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira