[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Shaikovsky resolved RF-7526.
---------------------------------
Resolution: Done
not a bug for sure.
about your original code:
suggestion box can't works correctly if DOM element to which it was attached
just replaced with another.
about changes Nick suggested:
also happens as designed. you can't reRender comboboxes, modal panels,
suggestions and other popup components parents after they shown. It will
replace elements on the page and re-initialize objects which will be cause of
such glitches. sorry for this suggestion.
If you need to update your input after suggestion request completed use just
oncomplete instead of just element replacement via reRender.
> Two use cases when rich:suggestion is displayed at the same time when the
> "for" field is re-rendered and a lot of related problems
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RF-7526
> URL: https://jira.jboss.org/jira/browse/RF-7526
> Project: RichFaces
> Issue Type: Bug
> Components: component-input
> Affects Versions: 3.3.1
> Reporter: Konstantin Spirov
> Assignee: Tsikhon Kuprevich
> Attachments: illustration-from-the-example.jpg, screenshoot2.jpg,
> test.xhtml, test.xhtml
>
>
> Wrong position of the suggestion box, that happens always in Mozilla & Opera
> - see the screenshots (in MSIE 8 you get JavaScript error in
> framework.pack.js instead).
> I am sending you as attachment a simple example (based on
> RichInput:SuggestionBox:ObjectsUsageExample). If you prefer to reconstruct it
> from your local copy of RichInput:SuggestionBox:ObjectsUsageExample, it is
> very easy. Just in rich:suggestion near for="statesinput" add
> reRender="statesinput" and the problem will appear.
> This bug is more deep then the concrete problem. Let me describe one
> meaningful and very important from business point of view scenario:
> Think we have not reRender="xxx" atribute in <rich:suggestionbox >, instead
> of this we combine the <h:inputText id="xxx"...> with
> <a4j:support reRender="xxx" event="onblur"...>
> In such scenario the same problem happens, but not always (from time to time
> - about 5% in my production when the "button" is pressed which is very nasty
> for the users). Surround everything
> in a4j:queue doesn't help, the problem happens in both modes.
> I hope you will agree that we often need reRender the field from
> <a4j:support...> (for example when the business logic on the server corrects
> the data automatically after the user input).
> This is the the exact problem (very major for us), but I am reporting it in a
> bit different form, because it gives you easier and always repeatable
> scenario.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
