[ https://issues.jboss.org/browse/RF-10657?page=com.atlassian.jira.plugin.s... ] Ilya Shaikovsky reassigned RF-10657: ------------------------------------ Assignee: Lukas Fryc Lukas please verify on final branch. http://richfaces-showcase.appspot.com/richfaces/component-sample.jsf?demo... Try the same with first autocomplete. It works for me. That's today build. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10657?page=com.atlassian.jira.plugin.s... ] Ilya Shaikovsky commented on RF-10657: -------------------------------------- Okay. I get the problem source. It works like there only if some token present in inserted String. Two reasons according to current impl: 1) we need to find where to place cursor after insertion. And we assume that after current insertion could be more strings separated with token like "alabama, ala, alabama" (let assume we inserting item instead of "ala"). So we looking for the next token to calculate new cursor position. 2) about second "Island" occurrence. Basically reason is the same. We need to erase direct suggestion so we trying to look to next token or end of text. So second 'Island' - just not eraced one after the token occurence. Talked to Pavel and we not sure that could implement that properly together with tokens support. And b.t.w. even if that will be implemented that single entry after insertion will be considered by the component as two words separated and will provide separate suggestion if you will try to edit them more. So I propose to document that as restriction and reject. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-10657?page=com.atlassian.jira.plugin.s... ] Jay Balunas updated RF-10657: ----------------------------- Fix Version/s: 4.Future (was: 4.1.0.Milestone1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira