Alright, I understand. Can't wait till it's released! Thanks for your
> Just one clarification. I wrote "I'll be working hard on that" but I
> actually meant "*we* will be working hard on that". I'm working basically at
> the front-end portion of our app but there's a great team of developers
> working on the back-end, which will allow us to bring the magic of
> JavaScript debugging to browsers such as Chrome and IE. Yeah, you heard it
> right: JavaScript debugging in IE! Isn't that awesome?
>
> regards,
>
> Pedro Simonetti.
>
>
>
>
>
>
>
>
> > Well, the answer is not that simple! :)
>
> > Firebug for Firefox uses a lot of APIs only available at Firefox, so the
> > Firefox and Chrome versions will never be the same.
>
> > On the other hand, if you are following our blog you may already know that
> > we are doing huge changes in Firebug architecture to allow remote debugging
> > and also better cross-browser support.
>
> > This means that we'll see in the future a lot of new features in Firebug
> > for Chrome, like JavaScript debugger, and possibly fully editing of HTML and
> > CSS, like you see in Firefox. And the best is that, once we get there, we'll
> > be using the same code base in Firebug and Firebug "Lite" (which will be not
> > so "lite" at that point), which means Firebug Lite will evolve a lot faster
> > than today.
>
> > But there's a long road ahead before we accomplish that, so I'm afraid it
> > will take a few months ( or not so "few" depending on your point-of-view :)
> > ). I cannot promise any dates but I'll be working hard on that, and I hope
> > this will happen by the end of this year.
>
> > In the meantime, if Firebug Lite does not offer all you want in Chrome, I
> > suggest you using Chrome Developer Tools. Also, if you want to follow our
> > progress I suggest reading our blog periodically:
>
> >
http://blog.getfirebug.com/
>
> > regards,
>
> > Pedro Simonetti.
>