Hi Joe,
unfortunately I didn't get any response from the list, although I tried
it two times.
I opened a bug report in jira but did not get any comment on that.
Maybe I find some time to do a diff between 1.2.2 and 1.2.3 to find out
what changes have been made that could cause this behaviour.
Joe Rossi schrieb:
Harald (anyone) - did you work out what's happening here? I think I'm
hitting something similar.
We've been successfully using 1.2.2 for a few months, but wanted to
move up to 1.2.5 in order to consume a couple of bug fixes that we
need. However, a number of our Selenium UI tests failed because of
clicks on command links not responding after dialogs had been displayed.
I've spent a bit of time trying to work out what's happening (not very
successfully). The only observations I have made are:
- The problem is intermittent but it only seems to occur after a
lightweight dialog has been launched and closed *and*if the closure of
the dialog results in a PPR refresh to a component on the underlying page
- With firebug I can observe a javascript error occurring when the
problem reproduces: _callChained is not defined DebugCommon1_2_5.js
line 8408. Also, firebug seems to indicate that there is a POST to the
server which has no response (though admittedly I'm not sure whether
this is correct or relevant?)
- I have tested Firefox and IE - it only seems to reproduce in Firefox
- I've tested 1.2.3 up to 1.2.5 and the problem reproduces in all
these versions (other issues are currently preventing testing of
1.2.6). Hence, it does seem like something that was introduced in 1.2.3.
Any clues anyone?
