Opened 13 years ago

Closed 13 years ago

#9016 closed enhancement (fixed)

Robot: support testing subdomains

Reported by: haysmark Owned by: haysmark
Priority: high Milestone: 1.4
Component: TestFramework Version: 1.3.0rc2
Keywords: Cc:
Blocked By: Blocking:


Under default browser x-domain policy, the robot can't test a page, for instance, on, if the test file lives on In particular, if you are testing an app that navigates across subdomains like these, the browser throws a Permission Denied error and the robot simply stops working.

The DOM Level 1 spec has a standard attribute called document.domain that is designed to let you get around this limitation for pages on the same superdomain ( But because the robot uses an iframe to load the applet environment, no one tells the iframe about the document.domain change, so you still see Permission Denied errors.

We could very easily enhance the robot to propagate this standard variable to the iframe. In doing so, we would gain support for testing more structurally complex apps that pull in data from servers living on other subdomains.

Attachments (1)

documentdomain.patch (2.2 KB) - added by haysmark 13 years ago.
Fixes #9016. Add support for document.domain to the doh.robot.

Download all attachments as: .zip

Change History (5)

Changed 13 years ago by haysmark

Attachment: documentdomain.patch added

Fixes #9016. Add support for document.domain to the doh.robot.

comment:1 Changed 13 years ago by haysmark

Milestone: tbd1.3.1

Attached prototype fix.

comment:2 Changed 13 years ago by bill

Is there a reason this needs to go into 1.3.1 instead of 1.4? 1.3.1 is only for critical bugs.

comment:3 Changed 13 years ago by Adam Peller


comment:4 Changed 13 years ago by Douglas Hays

Resolution: fixed
Status: newclosed

(In [17476]) Fixes #9016. Proxy commit for haysmark. Add support to the doh.robot for user-specified document.domain.

Note: See TracTickets for help on using tickets.