[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
Ján Jamrich commented on RF-12268:
----------------------------------
I've updated page with issue simulation.
Firstly I understood it wrong - I missed fact that second command button is conditionally
rendered (I thought it had disappeared accidentally).
So now it example contains 2 buttons, first with action handler with 3s delay, and with
updating variable value which is used as condition to render second command button.
(Note: you should get this application (Metamer) from git@github.com:richfaces/qa.git
(module Metamer/application) to play around this example. I referred to this example
running on my laptop in my comment above.
4.1.0.final javascript error : element is null, ajax queue operation
--------------------------------------------------------------------
Key: RF-12268
URL:
https://issues.jboss.org/browse/RF-12268
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component
Affects Versions: 4.1.0.Final
Reporter: zhifu Jin
Labels: richfaces, waiting_on_user
Original Estimate: 1 day
Remaining Estimate: 1 day
the issue is when have two requests like below will cause js error:"element is
null" and browser crash.
1. first request sending, and don't have response arrived.
2. the second request start, will add this request into queue.
3. first response arrived , the second request will be dequeue and send
request, it will find source element first, and our page had changed, the element is
null.
--
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