please attach simple warr sample for investigations.
Thank you for your flash reply!
Here is my war file which works fine in all browsers (with commented a4j:commandButton). Interactive chart stops to be interactive after uncomenting RichFaces button (It may be any other RichFaces component, and refers only to IE).
greeter4.war 9.2 MB
How about your investigations? Maybe some additional information is required for you?
As for me – I tried this sample with different versions of JSF and RichFaces (PrimeFaces version 1.0.1 - only) but result was the same. Any RichFaces component in a form and interactive chart stop working(((
Any other ideas or suggestions? Thanks!
I've checked .war file you've sent and the only problem I noticed is that clicking on chart in IE does nothing. Is it the problem?
There are no JS errors, it just doesn't work so I'm going to continue investigation with debugger when I get more time.
As immediate workaround, I can suggest you to try a4j:support.
Hi, Nick! Thanks for reply!
Not exactly my problem. The .war file I’ve sent is workable in IE and other browsers (you can check it while clicking on chart’s series – top string would show clicked item and series index).
I deploy it under JBoss 4.2.3.
There is commented a4j:commandButon in a index.jsf file, if I remove comments from it – chart stops to be interactive (top string does not update after clicking on the chart series). After my investigations I discovered that it may be any other RichFaces component (rich:modalPanel), which would also prevent the chart’s series click processing – and that is the problem.
Problem refers to the IE only, in FF it’s ok in both cases.
What is the difference for IE of processing the flash element or some JS with presence of the RichFaces components and their absence on the page?
could be some script dependencies conflicts.. some global variables or method overriden and so on.. And different browsers interpret some problems in a different way. E.g. if method with some name was overriden with just variable with the same name - one browser could just report error and the second will continue execution.. So really need some time to investigate this.
Your investigation results will be very much appreciated!
I hope the way of compatible two libraries usage without any conflicts exists…