#543 ✓wontfix
notalifeform (at gmail)

selenium & htmlunit ssue

Reported by notalifeform (at gmail) | January 16th, 2011 @ 09:51 AM | in 1.3 (closed)


This is probably a selenium/htmlunit/jquery issue, but Guillaume asked to file a bug anyway (see http://groups.google.com/group/play-framework/browse_thread/thread/...)

This issue:

If you want to make sure all ajax calls have finished, you can check a jquery property, see:

so the the call is

selenium.browserbot.getUserWindow().$.active == 0

which works fine under firefox, but breaks under htmlunit with the message
"Cannot read property "active" from undefined"

for some reason the jquery object is not accessible (Or I'm looking the wronh place).

under firefox 3.6.13 this works fine.

Framework version:
Framework version: play-1.1

Platform you're using:

Reproduction steps:

play new ajaxtest

create a test ./test/ajax.test.html containing:


waitForCondition('selenium.browserbot.getUserWindow().$.active == 0',5000)
assertNotTitle('Application error')


run play auto-test


ajax.test.html will fail with the message: "Cannot read property "active" from undefined"

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.