admin管理员组

文章数量:1200972

I'm using Facebook Connect in my app. I have it working pretty well, but in the Safari Error console, I'm seeing errors like this:

Unsafe JavaScript attempt to access frame with URL http://...#... from frame with URL .phpapi_key=..&extern=2&channel=http...xd_receiver.htm.
Domains, protocols and ports must match.

The app seems to function ok, though we are seeing periodic hangs and other bad behavior from Safari. When I run other Facebook Connect apps, I sometimes see this error too, so I don't think this is a problem with our implementation. Is it safe to ignore this warning?

I'm using Facebook Connect in my app. I have it working pretty well, but in the Safari Error console, I'm seeing errors like this:

Unsafe JavaScript attempt to access frame with URL http://...#... from frame with URL http://www.connect.facebook.com/extern/login_status.phpapi_key=..&extern=2&channel=http...xd_receiver.htm.
Domains, protocols and ports must match.

The app seems to function ok, though we are seeing periodic hangs and other bad behavior from Safari. When I run other Facebook Connect apps, I sometimes see this error too, so I don't think this is a problem with our implementation. Is it safe to ignore this warning?

  • javascript
  • safari
  • facebook
  • warnings
Share Improve this question edited May 14, 2009 at 8:10 annakata 75.8k18 gold badges115 silver badges181 bronze badges asked May 13, 2009 at 16:01 wolffiexwolffiex 4822 gold badges5 silver badges11 bronze badges 0
Add a comment  | 

3 Answers 3

Reset to default 3

Safari's cross frame security is tighter than other browsers, I have done specific try/catch wrappers to handle these cases, if it otherwise works, great.

Either way, would post the bug upstream as olliej suggests.

It means you're attempting some form of cross origin access, which is unsafe -- while it may seem benign it's probably worth trying to find out why you're hitting it, if you use the nightlies or the Safari4 beta you can use the debugger in the web inspector, and make it break on all exceptions, which will let you see when it's actually attempting the cross-origin access.

As for the hangs, if you can find some kind of reduced testcase it would be great if you could file them at http://bugs.webkit.org

This is a red herring. The request still goes through and everything is working properly but WebKit still logs an exception.

本文标签： Unsafe JavaScript attempt to access frame warning in SafariStack Overflow

版权声明：本文标题：Unsafe JavaScript attempt to access frame warning in Safari - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1738608912a2102517.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。