#1356 new
Jonas Kilian

Play testrunner: consider setting document.domain=document.domain

Reported by Jonas Kilian | January 4th, 2012 @ 05:09 PM

A well known issue for Selenium 1 is the same-origin policy, one of the main points for Selenium 2 / Webdriver to provide full-blown browser plugins/addons, I think.

In Selenium 1, the same-origin policy is typically worked around by installing a proxy, see http://wiki.openqa.org/display/SEL/Selenium+Core+FAQ#SeleniumCoreFA...

For Play's testrunner, I used not to have any issues with this, as AUT and Testrunner always run on the very same domain. However, as soon as I started to set "document.domain" in my AUT, testrunner stops working, showing the well known complaint:

Permission denied for http://subdomain.me.local:9000 to get property Location.href

My current workaround in my AUT itself looks like this:

    if(!window.location.href.indexOf("test-runner")) {

Now I wonder whether Play's testrunner could set document.domain explicitly like described here: http://stackoverflow.com/questions/1481251/what-does-document-domai...

I tested it with a stripped down version: Setting the above allows a page to access Iframe location even if the included HTML (the AUT in case of testrunner) sets document.domain explicitly.

What do you think?


No comments found

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.

People watching this ticket