Yeah, sorry about that.  The inspector is currently broken in the dev
release.  It's fixed in the tip of tree and should be out in the next
release (likely this week).
Erik


On Wed, Jun 10, 2009 at 2:00 PM, Nebojša Ćirić <[email protected]> wrote:

> I tried that too, but as I said, tools are broken for me. JavaScript
> console window looks badly rendered (has frame, you can click on a button
> that shows command line, but that's about it). See bug
> http://code.google.com/p/chromium/issues/detail?id=7800
>
> Cira
>
>
> On Wed, Jun 10, 2009 at 1:21 AM, Guria <[email protected]> wrote:
>
>>
>> Have you tried to right click on toolstrip.
>> As I know that should bring up devtools running in yurs toolstrip
>> envionronment.
>>
>> On 10 июн, 03:53, Nebojša Ćirić <[email protected]> wrote:
>> > I am on Vista 64, Chrome dev ver. 3.0.183.1
>> >
>> > I am building simple continuous build extension (fetches last status
>> > from the server, as text file, parses result, and sets toolstrip
>> > button).
>> >
>> > Problems:
>> >
>> > 1. My javascript console is blank. Even simple javascript: console.log
>> > (1); doesn't do anything. In fact there was a bug filed, but it seems
>> > it was closed in April (I can look up exact bug number).
>> >
>> > 2. In my background page when I iterate over views I get back 1
>> > element, backend page itself. Code looks like:
>> >
>> > ...
>> >   var views = chrome.self.getViews();
>> >   for (var i in views) {
>> >       if (views[i].toggleStripStatus)
>> >         views[i].toggleStripStatus(status);
>> >   }
>> > ...
>> >
>> > It's pretty hard to debug this (since console is out, and this is
>> > backend page so alerts don't work), but I managed to inspect views
>> > variable, and it has only 1 element, and that element is backend page
>> > itself.
>>
>>
>>
>
> >
>

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

Reply via email to