[JBoss JIRA] Created: (RF-7526) 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
9:41 a.m.
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
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
9:43 a.m.
New subject: [JBoss JIRA] Updated: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Konstantin Spirov updated RF-7526:
----------------------------------
Attachment: test.xhtml
The source if you need it - it is actually very similar to this in RichFaces showcase
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
Attachments: 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
9:51 a.m.
New subject: [JBoss JIRA] Updated: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Konstantin Spirov updated RF-7526:
----------------------------------
Attachment: the-problem-in-production.jpg
Illustration from the real product
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
Attachments: test.xhtml, the-problem-in-production.jpg
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
9:55 a.m.
New subject: [JBoss JIRA] Updated: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Konstantin Spirov updated RF-7526:
----------------------------------
Attachment: illustration-from-the-example.jpg
Illustration from the example - this time with Firefox
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
Attachments: illustration-from-the-example.jpg, test.xhtml,
the-problem-in-production.jpg
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
10:54 a.m.
New subject: [JBoss JIRA] Updated: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Nick Belaevski updated RF-7526:
-------------------------------
Attachment: (was: the-problem-in-production.jpg)
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
Attachments: illustration-from-the-example.jpg, 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
9:25 a.m.
New subject: [JBoss JIRA] Commented: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Konstantin Spirov commented on RF-7526:
---------------------------------------
If you need test platform for scenario 2 (with <a4j:support reRender="xxx"
event="onblur") use https://jira.jboss.org/jira/browse/RF-7527 for reference
(see where RF-7526 is mentioned in the text)
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
Attachments: illustration-from-the-example.jpg, 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
1:04 a.m.
New subject: [JBoss JIRA] Reopened: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Konstantin Spirov reopened RF-7526:
-----------------------------------
If you reRender the parent component, the things become even worse. See the screenshoot
(with opera) and the new code of the xhtml. The code is *just as you recommended*, but the
results are disasterous!
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, 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
1:08 a.m.
New subject: [JBoss JIRA] Updated: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Konstantin Spirov updated RF-7526:
----------------------------------
Attachment: screenshoot2.jpg
The screenshoot of the test scenario, based on your recomendation. You see, that the
sugestion box is not only on wrong position, but also painted twice at different places.
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
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
1:10 a.m.
New subject: [JBoss JIRA] Updated: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Konstantin Spirov updated RF-7526:
----------------------------------
Attachment: test.xhtml
New version of the simple test.xhtml, based on your recommendation.
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
8:31 a.m.
New subject: [JBoss JIRA] Reopened: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Ilya Shaikovsky reopened RF-7526:
---------------------------------
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
8:31 a.m.
New subject: [JBoss JIRA] Resolved: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
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
8:31 a.m.
New subject: [JBoss JIRA] Resolved: (RF-7526) 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
[
https://jira.jboss.org/jira/browse/RF-7526?page=com.atlassian.jira.plugin...
]
Ilya Shaikovsky resolved RF-7526.
---------------------------------
Resolution: Rejected
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
5470
days inactive
5472
days old
richfaces-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Ilya Shaikovsky (JIRA) -
Konstantin Spirov (JIRA)
-
Nick Belaevski (JIRA)