Phew... I would have agreed if u guys had said I was crazy too... I
follow these threads to understand and learn new stuff... :)

-Nischal

On May 20, 12:07 am, Steve C <[email protected]> wrote:
> I am assuming they will create a dummy function that will be used
> console.log is undefined- otherwise, you are very right.
>
> On May 19, 3:03 pm, nischalshetty <[email protected]> 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 <[email protected]> wrote:
>
> > > On Wed, May 19, 2010 at 11:27 AM, Steve C <[email protected]> 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
> > > [email protected] / @danwrong
> > > +1 415 425 5631

Reply via email to