Noo.. completely new!? all the bugs reintroduced!
On 8/28/08, Matej Knopp [EMAIL PROTECTED] wrote:
Probably not for 1.3/1.4. We could have something like that for 1.5
(where the ajax pipeline is completely new).
-Matej
On Thu, Aug 28, 2008 at 6:23 PM, John Krasnay [EMAIL PROTECTED] wrote:
I'm testing some Ajax-y Wicket pages with Selenium. One challenge I'm
having is finding a good expression to use in Selenium's
waitForCondition. Right now I wait for the results of the Ajax call,
e.g. an appropriate element appearing, but it's sometimes difficult to
get this right, e.g. if a
Probably not for 1.3/1.4. We could have something like that for 1.5
(where the ajax pipeline is completely new).
-Matej
On Thu, Aug 28, 2008 at 6:23 PM, John Krasnay [EMAIL PROTECTED] wrote:
I'm testing some Ajax-y Wicket pages with Selenium. One challenge I'm
having is finding a good
OK, I've raised WICKET-1808 to track it.
If anyone's interested, the following seems to work. Define the
following script on your page:
wicketAjaxBusy = function() {
for (var c in Wicket.channelManager.channels) {
if (Wicket.channelManager.channels[c].busy) {
