sahi permission denied problem (controller window info -empty)

mcleris

Hallo,
Sahi works fine with all tested web pages, but facebook. When I try to access facebook, sahi control window is slightly different and info tab contains no information. If I try it with IE, I can observe the problem : "permission denied". My ssl and other protocols are set to localhost:9999. I have also created the certificate and did other steps, described in sahi tutorial and video. This doesn't help. And the problem is happening just with a facebook site.

Thank you in advance for your help

ytch

Hi,

I also meet the same problem,
when I open sahi controller in this website: tw.yahoo.com
firefox will show a Javascript Error: Permission denied to access property '_sahi'

return window.top.opener._sahi.top(); controller7.js（Line 140 ）

and it seems like sahi is called from different url: tw.rd.yahoo.com/_s_/spr/controller7.htm

narayan

Hi,

Facebook sets the domain to facebook.com (the base domain)
To make Sahi work, you need to add the URL pattern and base domain to sahi/userdata/config/domainfix.txt like below
*.facebook.com facebook.com

This will work only in the latest versions of Sahi and Sahi Pro. If you are using an older version, follow this: http://blog.sahi.co.in/2008/07/testing-applications-with-different.html

Regards,
Narayan

rashmipathak

Hi,

I am also getting the same problem Permission denied to access property '_sahi'.

I start recording from http page and then i go to https page and stop recording there, i get this above error.

I am trying with Sahi Build 2011-04-04.
Followed the step mentioned http://blog.sahi.co.in/2008/07/testing- … erent.html
Still facing the same error.

Details of the OS and browser are as follows:
OS Name: WindowsXp
Browser Name and Version : Mozilla Firefox 6.0

Sumitra

Hi rashmipathak,

The error generally happens when you start recording on windowA, windowA opens windowB, you perform actions on windowB and then windowB is closed. When you press Stop now, you would get the error.

The reason is that the Controller associates itself to the last opened window, and if the last window is closed, it is no longer associated with any base window. The way to resolve it, is to go to windowA and do a ALT-DblClick on the page, which will reassociate the window and Controller properly. There will be no loss of information, as the Controller's state is always maintained in the Proxy. You can even close and reopen the Controller without any problem.

Let me know if you face any problem.

Regards
Sumitra