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
At the moment, no. You'll need to do that yourself. Not too
difficult though, since @Anywhere stamps each link with a class of
twitter-anywhere-user. So, you could iterate over all anchor
elements, and if they have that class add the target attribute with
a value of _blank.
- Todd
On Tue, Jun
Hi @semel -
Still experiencing this problem with ShareThis and @Anywhere? If so,
can you send an URL or some sample code so that we can figure out what
the problem is? Thanks.
- Todd
On Fri, Jun 4, 2010 at 10:28 AM, LeeS - @semel lse...@gmail.com wrote:
I get this Javascript error when
Hey Scott -
If you've already linkified Twitter usernames yourself according to
the pattern used by the @anywhere linkifyUsers() method (@a
href=../a, then you can tell hovercards not to linkify as
follows:
twttr.anywhere(function (T) {
T.hovercards({ linkify: false });
});
If your anchor
There is a known bug in the @anywhere application creation flow that
results in @anywhere applications having read-only access. This
results in @anywhere widgets like the TweetBox and Follow Button not
working.
We just rolled out a fix to all currently registered @anywhere
applications.
