Re: [twitter-dev] Re: alert() in anywhere.js

2010-05-19 Thread Dan Webb
On Wed, May 19, 2010 at 12:03 PM, nischalshetty wrote: > One of us is crazy here. If I'm not wrong console.log belongs to > firebug. Which means you will get a javascript error on ALL browsers > which do not have firebug installed and running. > We were going to detect console.log's presence befo

Re: [twitter-dev] Re: alert() in anywhere.js

2010-05-19 Thread Dan Webb
On Wed, May 19, 2010 at 11:48 AM, Damon Clinkscales wrote: > On Wed, May 19, 2010 at 1:41 PM, Dan Webb wrote: >> On Wed, May 19, 2010 at 11:27 AM, Steve C wrote: > Just wondering...does TwitPic have a bug or misconfiguration or is > this an @anywhere bug? Javascript errors at startup time (in

Re: [twitter-dev] Re: alert() in anywhere.js

2010-05-19 Thread Damon Clinkscales
On Wed, May 19, 2010 at 1:41 PM, Dan Webb wrote: > On Wed, May 19, 2010 at 11:27 AM, Steve C wrote: >> We just rolled out @anywhere yesterday and some of our users are >> experiencing similar issues. >> >> http://twitpic.com/1p00d6 > > We rolled out a fix at the weekend that we fixed all the brow

Re: [twitter-dev] Re: alert() in anywhere.js

2010-05-19 Thread Dan Webb
On Wed, May 19, 2010 at 11:27 AM, Steve C wrote: > We just rolled out @anywhere yesterday and some of our users are > experiencing similar issues. > > http://twitpic.com/1p00d6 We rolled out a fix at the weekend that we fixed all the browsers that we test under but there are obviously still some

Re: [twitter-dev] Re: alert() in anywhere.js

2010-05-16 Thread Dan Webb
This does sound like a regression of some kind. We'll get this fixed ASAP. On Sat, May 15, 2010 at 3:41 PM, JohnB wrote: > > Are we really talking about incorrect installations here? Twitter's > own @Anywhere documentation page (http://dev.twitter.com/anywhere/ > begin) is throwing this same err

Re: [twitter-dev] Re: alert() in anywhere.js

2010-05-15 Thread Abraham Williams
Chrome has it too. On Sun, May 16, 2010 at 03:20, nischalshetty wrote: > Isn't console.log() specific to firebug? #JustSaying :) > > On May 16, 4:43 am, Larry wrote: > > Firefox 3.X is a supported browser for @anywhere and my example is > > properly configured, yet it triggered when it wasn't su

Re: [twitter-dev] Re: alert() in anywhere.js

2010-05-15 Thread Abraham Williams
I agree that @Anywhere should degrade gracefully when configured properly on unsupported platforms and not prompt incorrect alert()s. But I do think alert()s are probably the best way to notify developers of incorrect installations. Abraham On Sat, May 15, 2010 at 11:55, Larry wrote: > I can re