We are seeing the same behavior on http://www.mapleprimes.com
Any chance this will be fixed in @anywhere? If not, we'll likely need to remove @anywhere from our site. On Jun 1, 10:57 am, Steve C <st...@twitpic.com> wrote: > Right, I understand that it's not supported on older browsers but I > think that it's unacceptable behavior for @anywhere to redirect a user > from our site to a broken page on twitter.com. It seems like a defect, > even if the browser is not supported (it should just do nothing- not > cause issues). Is there anyway that @anywhere can do some browser > sniffing and cleanly exit out if the features you need are not > supported? > > Thanks, > > Steve Corona > Twitpic > > On Jun 1, 9:57 am, Taylor Singletary <taylorsinglet...@twitter.com> > wrote: > > > > > Hi Steve, > > > Sorry about the issues. @Anywhere supports the following browsers > > (fromhttp://dev.twitter.com/anywhere/begin): > > > Version 1 of @Anywhere supports the following browsers: > > > - Firefox 3.x > > - Chrome 4 > > - Safari 4 > > - Opera 10 > > - Internet Explorer 6, 7, and 8 > > > Taylor Singletary > > Developer Advocate, Twitterhttp://twitter.com/episod > > > On Tue, Jun 1, 2010 at 6:50 AM, Steve C <st...@twitpic.com> wrote: > > > We had some reports over the weekend of users using older browsers > > > (Firefox 2.0 was mentioned) being auto-redirected to "twitter.com/ > > > undefined" due to @anywhere. Anyone else having the same issue?
