-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NS_ERROR_NOT_AVAILABLE (Firefox) with AjaxStatus #2003
Comments
Does it also fail with 6.x? |
We have a relative large enterprise application, therefor I cannot "quickly" change to 6.x and recheck. |
Maybe a newer jquery version or something like that. |
Forget my complaints about the major update, I just replaced the jars and it was working. I can also reproduce this error in 6.0.13:
Am I right that you really need some sort of .xhtml and bean combination to reproduce this error, the stacktrace isn't enough? |
Yep. Stackrace is not enough in the most cases |
Please create a new issue with a sample or reopen this issue. Will close it for now. |
1) Environment
2) Expected behavior
Ajax requests work without problems.
3) Actual behavior
We sometimes see the JavaScript Error "NS_ERROR_NOT_AVAILABLE" in FireFox with the following StackTraces:
or
After this error no more ajax reqeusts get executed, which freezes our entire application.
4) Steps to reproduce
Hard to say. It seems like a timing problem, probably with multiple simultaneous ajax requests (remotecommand).
The problem doesn't occur, when we remove (rendered=false) the p:ajaxStatus component.
The p:ajaxStatus component is never rerendered/updated.
The text was updated successfully, but these errors were encountered: