-
1. Re: a4j:support focus should NOT select!
nbelaevski May 5, 2009 2:01 PM (in response to hanafey)Hello,
Thank you for reporting the issue: https://jira.jboss.org/jira/browse/RF-7025! -
2. Re: a4j:support focus should NOT select!
jrigby33 Mar 21, 2011 7:25 PM (in response to nbelaevski)I tried the suggested solution from the above link. This does work properly in Firefox, but the focus is put at the beginning of the text in IE. Is there any way to explicity set the focus at the end of the text to workout the IE bug?
<a4j:support event="onkeyup" ignoreDupResponses="true" requestDelay="100" reRender="templateGrid" oncomplete="#{rich:element('inputName')}.focus();"/>
-
3. Re: a4j:support focus should NOT select!
ilya_shaikovsky Mar 22, 2011 4:24 AM (in response to jrigby33)try workaround we used in our demo http://livedemo.exadel.com/richfaces-demo/richfaces/filteringFeature.jsf?tab=ex-usage&cid=76117
-
4. Re: a4j:support focus should NOT select!
jrigby33 Mar 22, 2011 9:49 AM (in response to ilya_shaikovsky)Thank you very much Ilya. That does exactly what I'm looking for.
One more minor thing I notice is that if you're typing at the moment the request processes, characters that were typed in during processing are removed. I notice it in my example much more than yours. I only have a delay of 100. When you delete characters is does just the opposite - adds characters back into the search box. From my perspective this isn't an issue, but I'm sure the users I am developing this for will notice it. They expect a quick refresh (little to no delay) which makes the issue more obvious.
It seems like the bean filter value isn't being set while the filter event is processing? Any tips? I tried adding an eventsQueue, but to no avail.
-
5. Re: a4j:support focus should NOT select!
ilya_shaikovsky Mar 23, 2011 7:04 AM (in response to jrigby33)old value returned from server and it's equals to the send one :/ So yes it's the case. But seems I could propose one more suggestion - use ignoreDupResponce set to true.