I think throw() seems more appropriate. Firebug and WebKit-based browsers will work with console.log(). A javascript error for an undefined function would still be better than an alert().
Larry On May 19, 12:03 pm, nischalshetty <nischalshett...@gmail.com> 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. > > -Nischal > > On May 19, 11:41 pm, Dan Webb <d...@twitter.com> wrote: > > > > > On Wed, May 19, 2010 at 11:27 AM, Steve C <st...@twitpic.com> 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 browsers getting the > > issue. I think we'll use console.info to display these message > > instead of an alert. We wanted to let developers know that they > > needed a clientID in the most noticable way but to avoid unintended > > annoyance of users we'll move to console.log. > > > Thanks, > > > -- > > Dan Webb > > Front-end Engineer, Platform > > d...@twitter.com / @danwrong > > +1 415 425 5631
