[twitter-dev] Re: anywhere back button bug in IE

[dndrnkrd]

Wanted to add that I've found this specific to use cases where
document.domain is set in config. The issue can be easily reproduced
in any IE browser with a simple test such as: http://gist.github.com/528661.
This one generates 2 extra history states, more can be created by
adding more iframe calls (ie, tweetBoxes).

[twitter-dev] anywhere back button bug in IE

[dndrnkrd]

As early as Monday, I'm getting reports of extra history states logged
in IE from my users. I've run my code that uses @anywhere with and
without anywhere.js on the page and have confirmed that 2 extra
history entries are being created by including the platform, and then
one new state is being logged for each twttr.anywhere call I make.
Could something have changed with the platform js recently that might
explain this?

[twitter-dev] Anywhere errors in Opera 10.6

[dndrnkrd]

Getting a continuous stream of the following in latest Opera/Mac. Call
stack looks to be trying to init a tweetbox, but I really can't debug
with the way opera scrolls to the latest error each time the console
updates. Any thoughts?

Uncaught exception: [object DOMException]
Error thrown at line 1, column 38190 in anonymous function:
twttr.postMessage(E, F) in 
http://platform1.twitter.com/1.1.2/javascripts/client.bundle.js:
F.postMessage(E,A);
called from line 1, column 40038 in J(N) in
http://platform1.twitter.com/1.1.2/javascripts/client.bundle.js:
twttr.postMessage(N,D)
called from line 1, column 40549 in M(N) in
http://platform1.twitter.com/1.1.2/javascripts/client.bundle.js:
J({ready:true,uuid:999});
called from line 1, column 38619 in anonymous function:
twttr._messageHandler(F) in 
http://platform1.twitter.com/1.1.2/javascripts/client.bundle.js:
D(E)
JavaScript - about:blank

[twitter-dev] Re: @anywhere iframes getting improper document domain?

[dndrnkrd]

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
  windo.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?

[twitter-dev] @anywhere iframes getting improper document domain?

[dndrnkrd]

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?