fidzu : Firebug

At least for that I would say, this info should be put to the wiki. For the other points I'm agreeing with you and Kevin. Of course additionally you could point to the wiki entries from posts in the news group.
Sebastian

31 Jul 2010 6:56am GMT

No, not only us two; the OP is bringing up bugs that others have
reported. Looking at the bugtracker:
2948: Console stops working (No XHR or log outputs)
With comment from " lisman.aaron, Apr 12, 2010" and " gullevek, Jun
17, 2010" confirming the same.
[link]

31 Jul 2010 6:42am GMT

I like the idea of a separate newsgroup.
Also, it might be worthwhile to require that all extensions listed on the
Firebug extensions page pass a set of requirements (Proper contact email,
some sort of testing certification). Devs would still be free to develop
extensions, but they wouldn't get the extra promotion that a listing on that

30 Jul 2010 7:45pm GMT

I would like to have a way to tell Firebug extension developers about
API changes, tests that fail with their extension installed, and
issues of extension conflicts.

We could use this newsgroup, but it seems like it might be more detail
than other readers may want to see.

I also need a way to send email directly to specific extension author

30 Jul 2010 7:29pm GMT

I've taken a pass at the firstrun and contribute pages. Start with
[link]
to see what users will see.

Next step is to set up the accounts and link them to the contribute
page.

jjb

30 Jul 2010 7:17pm GMT

Use FF 3.6 for Firebug 1.6.

jjb

On Jul 30, 11:24 am, Webdesign Tvorba webových stránek

30 Jul 2010 7:13pm GMT

FF 1.6 - i did not success to install this new version. I got report of
incompatibility
I have 3.5.11
2010/7/30 John J Barton <johnjbar...@johnjbarton.com>

30 Jul 2010 6:24pm GMT

A good place to start is
1. Open firebug tracing panel with option ERRORS
2. The first time you have a problem, check the trace.
3. Whether or not there is any info in the trace, describe exactly
what the problem is. 'net panel stops working' is not enough. Is it
blank? is the Console panel still showing XHR? If you set NET on the

30 Jul 2010 6:21pm GMT

OK, but don't expect a lack of reports for a lack of errors.
Sometimes it is necessary to restart Firefox to get Firebug working.
SOmetimes just opening a new tab works and that is easier, so I
usually try that first. I have experienced all of the OP's 7 items, so
that's how I know.
I'm sorry I can't be of more help. I don't know what triggers the

30 Jul 2010 5:00pm GMT

Perhaps you will read our paper on this very subject,
[link]
[link]

jjb

30 Jul 2010 2:59pm GMT

On Jul 30, 6:13 am, Misha Nesterenko <misha.nestere...@gmail.com>
wrote:

Mozilla platform does not support column or character based
breakpoints. Break up the code into multiple lines.

jjb

30 Jul 2010 2:55pm GMT

Regarding the title question, the automatic testing results for
Firebug 1.6 in Firefox 4.0 are online:
[link]

You don't need the Compatibility Reporter. 1.6 works in FF 4.0 by
design.

This is a Firefox 4.0 bug, see [link]

I think it will be a while. The bugs that block Firebug probably won't

30 Jul 2010 2:54pm GMT

I really like the ability to export HAR files from Firebug and use
this file in other tools. I would like to export a HAR file from c#
code, but can't really see, if I can use the Firebug code for that. As
I udnerstand it, Firebug is implemented in Javascript, right? Do any
one know a good way of exporting HAR files from .NET?

30 Jul 2010 2:35pm GMT

Hi everyone --

Running FF 3.6.8 and FB 1.5.4:

This intermittent error is killing my web app. When I google the
error, I see that folks have been complaining about it for years. But
I can find no solution. There's a rumor that it's associated with some
FF plugin.

Does anybody have any insight into the error or any idea how to fix

30 Jul 2010 1:53pm GMT

Hello

I have a javascript code written in a single line, how can debug it? I
need to set breakpoints, some indication of currently executing
statement.

30 Jul 2010 1:13pm GMT

I'm testing Firefox 4 beta 2 and loaded firebug-1.6X.0a18, thanks to
Add-on Compatibility Reporter.
Firebug font redering appear blured when opened under the browser.
And font rendering is ok when firebug is in separate window mode.
Hope it help bring Firebug to Firefox 4 soon.
David

30 Jul 2010 12:52pm GMT

Is it possible to make the Javascript debugger break immediately when
some Javascript is run such that you can start stepping through
without having to insert a breakpoint beforehand?

Sometimes I find myself putting breakpoints all over the place because
I can't remember what Javascript function is triggered.

30 Jul 2010 12:33pm GMT

Thanks Bob and Richard for explaining this dilemma a bit!
As programmer you should know, that sometimes it's hard to find an
issue. And it's impossible, if you can't reproduce the problem
somebody is having. That's why the reporter and the developer have to
work together to solve the problem.
Unfortunately I am often seeing issues in the FB issues list, where

30 Jul 2010 10:29am GMT

I agree with Colin. Stephan, it's hard to find your actual comment.

@John:
In his issues he always referred to his website [link],
so I think this time he's also meaning this site.

@Stephan:
For me it also happens sometimes, that there's a bug in Firebug, which
I can't reduce to a small test case, because often it's hard to figure

30 Jul 2010 8:26am GMT

I'm pretty sure I've completely broken the testbot by committing a
bunch of changes to tests/content. I changed FBTest to remove
loadSubscript() so that we can see FBTest in Chromebug. That helps a
lot. As a side effect I removed ".wrappedJSObject" in a bunch of test
driver files. We don't understand why these are needed so I can't tell

30 Jul 2010 12:23am GMT

Ok so now that I've convinced you, the bad news ;-).

Event systems are very efficient in system resources and they avoid a
class of nasty bugs intrinsic to threading. But they rely on
developers to create code that runs to completion in a fixed amount of
time. Otherwise the event manager will either fail to be responsive,

29 Jul 2010 5:07pm GMT

Thanks for the pointers/references, John. We'll shift our thinking and
design to be event based.
I was hoping that a "crossfire front end" implementation of
"Firebug.middle" could be largely re-used across different browsers.
However, if we need to rely on event mechanisms/sockets provided by the

29 Jul 2010 4:20pm GMT

Cool! It would be great to have Eyal Benatav on board. As I told in
my previous message, access to external resources is a very-wanted
feature, and I'll be glad to see Eyal working to make this feature
available in a future Firebug Lite release. I'm pretty sure that users
will love this feature.
One of the things I'm working right now is improving Firebug Lite

28 Jul 2010 11:29pm GMT

I was able to contact Eyal Benatav who created the firebugger site. I
made a few suggestions and invited him to join us. He will be making
some changes soon then asking for more feedback. He ended his email
with:

"Furthermore I'd like to give you and the whole Firebug developers
community a thumbs up for your excellent work."

28 Jul 2010 7:11pm GMT

The purpose of the multi-thread design is responsiveness: you want the
UI to remain alive in the face of unpredictable and possibly long
running back-end process. There are other ways to achieve
responsiveness, eventing systems being the most common alternative.
(see eg [link])

28 Jul 2010 6:50pm GMT

I'm looking at the 1.7 work plan, specifically "1. Define a new interface
Firebug.Middle".
Generally, debuggers are multi-threaded - there is a UI thread where the
user presses buttons, and there is an event thread handling events coming
back from the debugger back-end broadcasting them to interested handlers.

28 Jul 2010 4:48pm GMT

As I outlined in our conf call last week, the 1.7 work plan is
starting to take shape.
[link]

Your questions and comments will help this plan take shape. We'll
discuss more in the call today.

27 Jul 2010 4:20pm GMT

2010/7/26 John J Barton <johnjbar...@johnjbarton.com>:
No doubt they are improperly using Firebug trademark. The "Firebug"
keyword is used all over the site, and there is not a single link and/or
explanation about the FWG and how this could is related to it and to
the Firebug for Firefox or Firebug Lite.

27 Jul 2010 2:31pm GMT

It looks to me as like a quite original MFA site. I think they target
search terms like "firebug ie" or "firebug internet explorer". That is
why they have there so much boilerplate textual content which makes a
little sense when reading by human. Their blogpost has title "Firebug
For Internet Explorer".

27 Jul 2010 9:15am GMT

It is a simple service ... type a url into their homepage, click go
and the site will open with Firebug Lite at the bottom.

I suspect they are calling it "IE Firebug" because they fear that
using "Firebug Lite" may cause legal problems.

It definitely makes sense to discuss any legal implications with them

27 Jul 2010 8:05am GMT