Re: [twitter-dev] @anywhere iframes getting improper document domain?
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 window www.example.com (document.domain has not been set) to get property Window.twttr from www.example.com (document.domain = http://example.com). My @anywhere app's primary domain is www.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 to http://example.com, and b) why this property get isn't permitted?
Re: [twitter-dev] anywhere link overriding
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 15, 2010 at 2:44 PM, Furkan Kuru furkank...@gmail.com wrote: Is there any possibility to change the anywhere links to include target=_blank attribute and value in order to open in a new window? -- Furkan Kuru
Re: [twitter-dev] @anywhere fails if ShareThis on the page?
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 trying to use @anywhere on the same page as a ShareThis widget. Error: Permission denied for [name of my site[ to get property Window.document from http://wd.sharethis.com. Source File: http://platform.twitter.com/anywhere.js?id=[my api key]v=1 Line: 1
Re: [twitter-dev] @anywhere hovercard events
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 elements include the @ symbol, and/or use a different
class name, you can configure hovercards as follows:
twttr.anywhere(function (T) {
T(.YOUR_CLASS_NAME).hovercards({ infer: true });
});
For more, see the docs: http://dev.twitter.com/pages/anywhere_begin#hovercards
- Todd
On Tue, Apr 20, 2010 at 9:09 AM, Furkan Kuru furkank...@gmail.com wrote:
I have just added class=twitter-anywhere-user manually to the links which
I want to show hovercards.
and just:
script type=text/javascript
twttr.anywhere(function (T) {
T.hovercards();
});
/script
On Tue, Apr 20, 2010 at 6:44 PM, scotth_uk satsc...@gmail.com wrote:
Hi, been playing with the @anywhere stuff, very excited about this!
I know its still a work in progress and things may change, but is
there a way to make hovercards() work as normal for onmouseover, but
let my javascript handle the onclick event, rather than sending the
user off to their twitter profile page?
Currently if I link @screenname myself, hovercards() ignores it, so
its one or the other.
Cheers,
Scott
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
--
Furkan Kuru
[twitter-dev] Read only @anywhere application bug fix
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. However, those creating new applications over the weekend will need to grant their application(s) write permissions by following these steps: 1) Go to: http://twitter.com/oauth 2) Click on your application 3) On the Application Details page click the Edit Application Settings button 4) On the settings page for your application, scroll down to the item labeled Default Access type 5) Change the Default Access type to Read Write We apologize for the inconvenience and will be deploying a fix for this early next week. We'll be sure to notify you all when the fix is rolled out. - The @anywhere Team -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
