Received: by 10.68.190.71 with SMTP id go7mr1433243pbc.8.1324153034582;
        Sat, 17 Dec 2011 12:17:14 -0800 (PST)
Path: lh20ni34075pbb.0!nntp.google.com!news2.google.com!postnews.google.com!cb3g2000vbb.googlegroups.com!not-for-mail
From: Ben <ben.will...@gmail.com>
Newsgroups: mozilla.addons.chromebug
Subject: Any updates on a new Chromebug?
Date: Sat, 17 Dec 2011 12:17:14 -0800 (PST)
Organization: http://groups.google.com
Lines: 16
Message-ID: <4a515df3-5e77-461e-8bbb-c313b68115d5@cb3g2000vbb.googlegroups.com>
NNTP-Posting-Host: 98.204.55.54
Mime-Version: 1.0
X-Trace: posting.google.com 1324153034 23667 127.0.0.1 (17 Dec 2011 20:17:14 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sat, 17 Dec 2011 20:17:14 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: cb3g2000vbb.googlegroups.com; posting-host=98.204.55.54; posting-account=q2KyNwoAAACp14hQOmOZht6sY0PWaZCm
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.2 (KHTML, like
 Gecko) Chrome/15.0.874.121 Safari/535.2,gzip(gfe)
Content-Type: text/plain; charset=ISO-8859-1

Is Chromebug dead?

Going through acrobatics to install FF5 to get a working version of
Chromebug - I can't see any other way of debugging an extension.

I'm putting a lot of time into developing a FF extension, but am
having second thoughts if there's no future for a debugger for this
environment. I'm not quite advanced enough to update Chromebug myself,
otherwise I'd offer my services.

Anyone else have any information or tips on this issue - and how to
debug XUL extensions?

Best,

Ben