[
https://issues.jboss.org/browse/RF-12158?page=com.atlassian.jira.plugin.s...
]
Lukáš Fryč edited comment on RF-12158 at 4/24/12 4:10 AM:
----------------------------------------------------------
As Cristian said, {{rich:autocomplete}} was designed in RF4 to do not produce any
side-effects with completion.
Any processing should be done using attached behaviors.
----
But...
[{{Autocomplete.js}}|https://github.com/richfaces/components/blob/develop/input/ui/src/main/resources/META-INF/resources/org.richfaces/Autocomplete.js#L189]
shows that it is using {{RichFaces.ajax(...)}} to do the request, which causes the regular
JSF AJAX request.
Then autocomplete's
[{{RendereBase}}|https://github.com/richfaces/components/blob/develop/input/ui/src/main/java/org/richfaces/renderkit/AutocompleteRendererBase.java#L264]
causes to hang this AJAX request prematurely when it identifies suggestion request.
But it isn't complete, since the ExtendedPartialViewContext will cause to add any
{{ajaxRenderer}} components to the response.
The solution would be to instruct ExtendedPartialViewContext to do
"{{limitRender}}" programatically.
----
This issue is similar to RF-9567, but the it has fixed the issue only partially, since it
is skipping validation.
was (Author: lfryc):
As Cristian said, {{rich:autocomplete}} was designed in RF4 to do not produce any
side-effects with completion.
Any processing should be done using attached behaviors.
----
But...
[{{Autocomplete.js}}|https://github.com/richfaces/components/blob/develop/input/ui/src/main/resources/META-INF/resources/org.richfaces/Autocomplete.js#L189]
shows that it is using {{RichFaces.ajax(...)}} to do the request, which causes the regular
JSF AJAX request.
Then autocomplete's
[{{RendereBase}}|https://github.com/richfaces/components/blob/develop/input/ui/src/main/java/org/richfaces/renderkit/AutocompleteRendererBase.java#L264]
causes to hang this AJAX request prematurely when it identifies suggestion request.
But it isn't complete, since the ExtendedPartialViewContext will cause to add any
{{ajaxRenderer}} components to the response.
The solution would be to instruct ExtendedPartialViewContext to do
"{{limitRender}}" programatically.
----
This issue is similar to RF-9567.
Autocomplete component re-renders panels with ajaxRendered=true at
each character being typed in into the autocomplete box
--------------------------------------------------------------------------------------------------------------------------
Key: RF-12158
URL:
https://issues.jboss.org/browse/RF-12158
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.2.0.Final
Environment: Windows 7, Chrome/IE/FF, Java 1.6, Tomcat 7, Spring 3.1
Reporter: Cristian Cerb
Assignee: Ján Jamrich
See this sample:
https://gist.github.com/2353552
And this forum entry:
https://community.jboss.org/message/729173?tstart=0
I tried to remove this: onkeypress="return submitOnEnter(event,
'#{rich:clientId('qsPayorSupcdCmdBtnId')}')"
and it worked fine. This JS piece of code produces a programatic button click when Enter
is pressed inside autocomplete box.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira