Todd, thanks! It's also an issue on the callback in other browsers, but manually setting that file's document.domain prior to including the @anywhere script seems to take care of that. So, this setting might be all I need at this point.
On Jul 9, 2:48 pm, Todd Kloots <klo...@twitter.com> wrote: > Hello, > > By chance are you only seeing this error in IE? If so, the following > config for @Anywhere can fix your problem: > > twttr.anywhere.config("domain", document.domain); > > - Todd > > > > On Fri, Jul 9, 2010 at 9:56 AM, dndrnkrd <dan.drink...@gmail.com> wrote: > > I'm seeing same-origin policy issues at the completion of the > > @anywhere sign-in process, to the tune of: "permission denied for > > windowwww.example.com(document.domain has not been set) to get > > property Window.twttr fromwww.example.com(document.domain = > >http://example.com). > > > My @anywhere app's primary domain iswww.example.com, and to boot, > > example.com is in my allowed domains as well. Any ideas on why a) the > > generated tweetbox iframe sets its domain tohttp://example.com, and > > b) why this property get isn't permitted?