2:28 a.m.
zhifu Jin created RF-12268:
------------------------------
Summary: 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
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
2:30 a.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin updated RF-12268:
---------------------------
Workaround Description:
I just changed packed.js by myself, like below:
if(R[0].getReadyToSubmit() ){
Z=T=R.shift();
N.debug("richfaces.queue: will submit request NOW");
var a=T.options;
a["AJAX:EVENTS_COUNT"]=T.eventsCount;
//modify by zhifu for "element is null" bug on 09 May, 2012
+ if(T.source && (typeof T.source==="object" || (typeof T.source
=== "string" && document.getElementById(T.source) ))){
E.ajaxContainer.jsfRequest(T.source,T.event,a);
+ }else{
+ T = null;
+ return;
+ }
//modify end
if(a.queueonsubmit){
a.queueonsubmit.call(Z)
}
J("onrequestdequeue",Z)
}};
was:
I just changed packed.js by myself, like below:
if(R[0].getReadyToSubmit() ){
Z=T=R.shift();
N.debug("richfaces.queue: will submit request NOW");
var a=T.options;
a["AJAX:EVENTS_COUNT"]=T.eventsCount;
//modify by zhifu for "element is null" bug on 09 May, 2012
+ if(T.source && (typeof T.source==="object" || (typeof T.source
=== "string" && document.getElementById(T.source) ))){
E.ajaxContainer.jsfRequest(T.source,T.event,a);
+ else{
+ T = null;
+ return;
+ }
//modify end
if(a.queueonsubmit){
a.queueonsubmit.call(Z)
}
J("onrequestdequeue",Z)
}};
Forum Reference: https://community.jboss.org/message/735917 (was:
https://community.jboss.org/message/735917)
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
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
2:30 a.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin updated RF-12268:
---------------------------
Workaround Description:
I just changed packed.js by myself, like below:
if(R[0].getReadyToSubmit() ){
Z=T=R.shift();
N.debug("richfaces.queue: will submit request NOW");
var a=T.options;
a["AJAX:EVENTS_COUNT"]=T.eventsCount;
//modify by zhifu for "element is null" bug on 09 May, 2012
+ if(T.source && (typeof T.source==="object" || (typeof T.source
=== "string" && document.getElementById(T.source) ))){
E.ajaxContainer.jsfRequest(T.source,T.event,a);
+ }else{
+ T = null;
+ return;
+ }
//modify end
if(a.queueonsubmit){
a.queueonsubmit.call(Z)
}
J("onrequestdequeue",Z)
}};
was:
I just changed packed.js by myself, like below:
if(R[0].getReadyToSubmit() ){
Z=T=R.shift();
N.debug("richfaces.queue: will submit request NOW");
var a=T.options;
a["AJAX:EVENTS_COUNT"]=T.eventsCount;
//modify by zhifu for "element is null" bug on 09 May, 2012
+ if(T.source && (typeof T.source==="object" || (typeof T.source
=== "string" && document.getElementById(T.source) ))){
E.ajaxContainer.jsfRequest(T.source,T.event,a);
+ }else{
+ T = null;
+ return;
+ }
//modify end
if(a.queueonsubmit){
a.queueonsubmit.call(Z)
}
J("onrequestdequeue",Z)
}};
Forum Reference: https://community.jboss.org/message/735917 (was:
https://community.jboss.org/message/735917)
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
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
5:44 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
Brian Leathem reassigned RF-12268:
----------------------------------
Assignee: Pavol Pitonak
QE, please confirm
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
Assignee: Pavol Pitonak
Labels: richfaces
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
6:33 a.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
Pavol Pitonak reassigned RF-12268:
----------------------------------
Assignee: Ján Jamrich (was: Pavol Pitonak)
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
Assignee: Ján Jamrich
Labels: richfaces
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
4:52 a.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
Ján Jamrich commented on RF-12268:
----------------------------------
Added page to simulate this issue (in current Metamer):
http://localhost:8080/metamer/faces/components/a4jQueue/rf-12268.xhtml
zhifu Jin, can you please check this page? (For more info about source see Source tab).
I'm not sure how your code looks like, maybe you did it another way. Because I
didn't get any problem you mentioned in description. Can you provide more detailed
code to simulate this issue?
In short, there is quick help how I used page mentioned above for issue simulation:
1. Click on button labeled: "Ajax action with delay" (there is called dummy
action handler, which has 3s delay before continue)
2. Click on button labeled: "Ajax action 2".
3. On the right top corner are listed phases and action handlers logs. There should
appear record like: "* action invoked [start]" and "* action invoked
[end]". Immediately after it simple "* action invoked" - action handler log
for second button.
Very similar when check "Introduce Delay" - just get delay before requests send.
It is better to see what happens.
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
Assignee: Ján Jamrich
Labels: richfaces
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
4:54 a.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
Ján Jamrich reassigned RF-12268:
--------------------------------
Assignee: (was: Ján Jamrich)
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
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
8:15 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin commented on RF-12268:
--------------------------------
I can't access your page
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
8:45 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin edited comment on RF-12268 at 5/22/12 9:45 PM:
---------------------------------------------------------
I can't access your page.
I had read your code. Your page a little different with ours. If you need add render
attribute for "action 1" and rendered for "action 2", and "action
2" will be delete, when "action 1" response arrived. it like this:
<a4j:commandButton id="ajaxAction1" render="action2Area"/>
<a4j:outputPanel id="action2Area" rendered="#{!action1Click}">
<a4j:commandButton id="ajaxAction2"/>
</a4j:outputPanel>
was (Author: war0071):
I can't access your page
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
8:47 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin edited comment on RF-12268 at 5/22/12 9:46 PM:
---------------------------------------------------------
I can't access your page.
I had read your code. Your page a little different with ours. You need add render
attribute for "action 1" and rendered for "action 2", and "action
2" will be delete, when "action 1" response arrived. it like this:
<a4j:commandButton id="ajaxAction1" render="action2Area"/>
<a4j:outputPanel id="action2Area" rendered="#{!action1Click}">
<a4j:commandButton id="ajaxAction2"/>
</a4j:outputPanel>
was (Author: war0071):
I can't access your page.
I had read your code. Your page a little different with ours. If you need add render
attribute for "action 1" and rendered for "action 2", and "action
2" will be delete, when "action 1" response arrived. it like this:
<a4j:commandButton id="ajaxAction1" render="action2Area"/>
<a4j:outputPanel id="action2Area" rendered="#{!action1Click}">
<a4j:commandButton id="ajaxAction2"/>
</a4j:outputPanel>
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
8:47 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin commented on RF-12268:
--------------------------------
Is this need I change status?
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
8:18 a.m.
[
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
9:26 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin commented on RF-12268:
--------------------------------
I got code, and run on tomcat7.0.27 had this error on rf-12268.xhtml page:
javax.faces.view.facelets.FaceletException: javax/servlet/jsp/jstl/core/LoopTagStatus
and I got nothing about log and console output. I checked the jstl lib of mine is 1.2
version. How I can enable the log of metamer application?
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
9:43 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
zhifu Jin commented on RF-12268:
--------------------------------
I had add one attach screenshot. Why I can't see it?
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
3:51 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-12268:
-------------------------------
Steps to Reproduce:
# click button send first ajax request to server, don't response it.
# click the button in your render area, the button will disappear when the response
arrived.
# the first response arrived.
was:
1. click button send first ajax request to server, don't response it.
2. click the button in your render area, the button will disappear when the response
arrived.
3. the first response arrived.
Workaround Description:
I just changed packed.js by myself, like below:
{code}
if(R[0].getReadyToSubmit() ){
Z=T=R.shift();
N.debug("richfaces.queue: will submit request NOW");
var a=T.options;
a["AJAX:EVENTS_COUNT"]=T.eventsCount;
//modify by zhifu for "element is null" bug on 09 May, 2012
+ if(T.source && (typeof T.source==="object" || (typeof T.source
=== "string" && document.getElementById(T.source) ))){
E.ajaxContainer.jsfRequest(T.source,T.event,a);
+ }else{
+ T = null;
+ return;
+ }
//modify end
if(a.queueonsubmit){
a.queueonsubmit.call(Z)
}
J("onrequestdequeue",Z)
}};
{code}
was:
I just changed packed.js by myself, like below:
if(R[0].getReadyToSubmit() ){
Z=T=R.shift();
N.debug("richfaces.queue: will submit request NOW");
var a=T.options;
a["AJAX:EVENTS_COUNT"]=T.eventsCount;
//modify by zhifu for "element is null" bug on 09 May, 2012
+ if(T.source && (typeof T.source==="object" || (typeof T.source
=== "string" && document.getElementById(T.source) ))){
E.ajaxContainer.jsfRequest(T.source,T.event,a);
+ }else{
+ T = null;
+ return;
+ }
//modify end
if(a.queueonsubmit){
a.queueonsubmit.call(Z)
}
J("onrequestdequeue",Z)
}};
Forum Reference: https://community.jboss.org/message/735917 (was:
https://community.jboss.org/message/735917)
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
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
3:53 p.m.
[
https://issues.jboss.org/browse/RF-12268?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-12268:
-------------------------------
Fix Version/s: 4-Tracking
Forum Reference: https://community.jboss.org/message/735917 (was:
https://community.jboss.org/message/735917)
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
Fix For: 4-Tracking
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
4355
days inactive
4432
days old
richfaces-issues@lists.jboss.org
15 comments
4 participants
participants (4)
-
Brian Leathem (JIRA) -
Ján Jamrich (JIRA)
-
Pavol Pitonak (JIRA)
-
zhifu Jin (JIRA)