Firebug / FireFox 3 Integration

[Timothy Farrar]

I downloaded both FireFox 3, and FireBug 1.2.0b3, and cannot get
firebug to even show.
Any ideas?

[John J Barton]

Please try to install in a new Firefox profile and let us know if that
works.


On Jun 25, 2:13 pm, Timothy Farrar <timothyfar...@sosensible.com>
wrote:

[Mark Kahn]

For me, FF3 works, FF3+FB = unstable + constant crashes on OSX.

Therefore, for me, FF3 = unusable.  :(

-Mark

--
Groucho Marx  - "A child of five would understand this. Send someone to fetch a child of five."

[John J Barton]

Use about:crashes as a URL to get the crash reporter URLs and post
them here or in a bugzilla.mozilla.org report.

I know of two crashes, one has a stack starting with
js_GetSrcNoteOffset which is FIXED
https://bugzilla.mozilla.org/show_bug.cgi?id=440473
Hopefully this will be in the next FF3.0

The other
Bug 439290 – Crash FF3 on mouse over with Firebug 1.2b3
https://bugzilla.mozilla.org/show_bug.cgi?id=439290
you haven't hit yet.

On Jun 25, 4:41 pm, "Mark Kahn" <cwol...@gmail.com> wrote:
> For me, FF3 works, FF3+FB = unstable + constant crashes on OSX.
>
> Therefore, for me, FF3 = unusable.  :(
>
> -Mark
>
> On Wed, Jun 25, 2008 at 2:13 PM, Timothy Farrar <
>

[Mark Kahn]

okay, well they're technically lockups when I have breakpoints set and reload a page.

-Mark

--
WC Fields  - "I am free of all prejudices. I hate every one equally."

[Timothy Farrar]

Sorry, I uninstalled Firebug, and then FireFox, and then downloaded
and installed both of them, but I get the same behavior.

On Jun 25, 8:36 pm, "Mark Kahn" <cwol...@gmail.com> wrote:
> okay, well they're technically lockups when I have breakpoints set and
> reload a page.
>
> -Mark
>

> On Wed, Jun 25, 2008 at 5:03 PM, John J Barton <johnjbar...@johnjbarton.com>

[John J Barton]

"The same behavior" as what?

On Jun 27, 6:49 am, Timothy Farrar <timothyfar...@sosensible.com>
wrote:

[John J Barton]

Sorry I don't know what a lockup is?

There are 13 bug reports with test cases against the Script panel. The
ones I have not fixed include three issues:
* breakpoints in iframes
* performance on 40,000 line sources
* unexpected single step behavior.
I will fix the first one. The second has existed since Firebug was
born; I'll take a shot but its complex. The third is not under
Firebug's control.

So if you have problems with Javascript debugging, please create a
test case and add it to the issues list. You may think your problem is
so common that everyone would have hit it, but this is surprisingly
unlikely. There are so many different ways people use Javascript that
testing all of the paths is quite difficult.

John.

On Jun 25, 5:36 pm, "Mark Kahn" <cwol...@gmail.com> wrote:
> okay, well they're technically lockups when I have breakpoints set and
> reload a page.
>
> -Mark
>

> On Wed, Jun 25, 2008 at 5:03 PM, John J Barton <johnjbar...@johnjbarton.com>

[Timothy Farrar]

OK... Got fireBug working. Had to uninstall firefox and all my data,
plugins ect. and then go back and re-install my plugins.

The behavior mentioned above was that the firebug icon showed in the
bottom right hand corner of my browser, but we could not get it to
launch.

Wish I could have got it working though without uninstalling
everything, and erasing all my personal data... maybe there is another
approach I could have taken, and if so, please point it out for my
benefit, and the benefit of others with this issue...

Otherwise I am very happy with the updates to both firefox and
firebug...

thanks

Timothy

[John J Barton]

If by personal data you mean bookmarks, I think they can be copied to
your new profile. Look around Firefox docs.

On Jun 30, 6:51 am, Timothy Farrar <timothyfar...@sosensible.com>
wrote:

[Rako]

I think there IS an other approach:
A list of for debugging "essential" extentions that are known to work
with FB and each other.
and another that are known to cause problems.
Of course there are a lot in-between you can use.
If you want to ba safe, you install just the safe ones, if you are
ready to risk a crash or that FB misbehaves, you can try out the buggy
ones (often not officially released but would be very useful in the
future, if they can be got to work - Rainbow for FB)
With the large number of extensions - often more than one providing a
feature in different forms - it is likely that some extensions are not
compatible with each other although the are compatible with FF3 anf FB
on their own.
With the large number of extensions, we cannot expect the developers
to test every combination. That can only be done by users experiencing
a problem that is caused by such to report the incompatibility.

Perhaps a matrix would be the best solution.

As for the crashes: I had a number of them, when I did not access FF.
I was using some other program or going from one to another, when
suddenly I got a FF-crash notification - saying that it could not be
reported.
I will have to try out the method named earlier in this topic.

On Jun 30, 3:51 pm, Timothy Farrar <timothyfar...@sosensible.com>
wrote: