This has happened a few times already - does the Web Inspector really have a
priority that low so you can release Dev updates with a non operational Web
Inspector?(General knowledge question.)

And this time it was not even mentioned in the release notes...

Is it possible (on your end) to make sure that it works for future
releases..?

I know me and my some of my co-workers are using it all of the time to debug
web pages in out job (I know this is totally unrelated to Chrome and kind of
our problem for choosing the Dev channel, but it sometimes has improvements
that are helpful for us) and every time there is a version with a broken Web
Inspector, it disturbs our workflow and we do not want to revert to an old
Beta or Stable version just to get the Web Inspector working...

We used to use FireBug, but once I discovered your fabulous Web Inspector, I
switched right on (browsing was already yours ;)).


(Sorry if I sound too complaining. I really appreciate all of your hard
works and go along with everything you are releasing, happily.)

Thank you, anyway.

☆PhistucK


On Fri, Jun 5, 2009 at 19:36, Aaron Boodman <[email protected]> wrote:

>
> This is a known issue in the current dev channel. It will be fixed in
> the next update. If you want, you can try using a trunk build from
> http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/ until
> then. Note that these builds are created automatically with no manual
> testing, so quality varies. But the inspector bug has been fixed
> there.
>
> - a
>
> On Fri, Jun 5, 2009 at 9:30 AM, AlexItelman<[email protected]> wrote:
> >
> > The inspector dialog appears to be empty no matter what I try to
> > inspect... empty = no buttons on the top, only a search box, I can
> > open the console on the bottom, but nothing happens when I try to
> > evaluate an expression there
> > >
> >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---

Reply via email to