02 Nov 2017

feedFirebug

Re: firebug html tab is empty after new firefox upadated

As Erik and I wrote earlier, the development of Firebug is discontinued and it stops working completely in Firefox 57 (released on 2017-11-14), so it's time to say goodbye to Firebug. The suggested solution is to use the Firefox DevTools instead. For everyone unfamiliar with them, there's a

02 Nov 2017 12:17pm GMT

01 Nov 2017

feedFirebug

Re: firebug html tab is empty after new firefox upadated

What is the Solution for the Below am also facing the same problem? what Hazuan Nazri faceing? Hello guys, today, after i update my firefox, my firebug is not working properly. the HTML tab is empty but other tab is working good. maybe you can refere to the attachment. "Inspect Elemnt With

01 Nov 2017 11:34am GMT

25 Oct 2017

feedFirebug

Re: [firebug] Saying Goodbye to Firebug

Hi Jan and Team, even if it can not compensate the hours and hours of work you putted into this projekt... Thanks for all what you have done on it !! Best regards schubi Jan Honza Odvarko schrieb: Hi All Firebug users, support for every old-school (XUL & Add-on SDK based) extension stops in

25 Oct 2017 9:32am GMT

Saying Goodbye to Firebug

Hi All Firebug users, support for every old-school (XUL & Add-on SDK based) extension stops in Firefox Quantum (aka 57). Yes, including Firebug. I wrote a post about Firebug history and the work done by Firebug community over the last 12 years. Explaining the current status as well as celebratin

25 Oct 2017 5:58am GMT

23 Oct 2017

feedFirebug

Re: Firebug not comfortable Ubuntu Firefox 56.0 (64-bit)

Firebug's development is officially discontinued. Firebug users are encouraged to use the Firefox built-in developer tools instead. See https://hacks.mozilla.org/2016/12/firebug-lives-on-in-firefox-devtools/ for more info. Sebastian On Monday, October 16, 2017 at 1:42:28 PM UTC+2, vithul nk

23 Oct 2017 8:41am GMT

20 Oct 2017

feedFirebug

Re: firebug html tab is empty after new firefox upadated

Just to be clear, staying with an outdated version of a software is normally not recommendable, because you miss security and other bug fixes and also new features. Firebug users are advised to try out the Firefox DevTools. And if you don't like them or miss a feature Firebug had, you should

20 Oct 2017 12:23pm GMT

Re: [firebug] firebug....is a bug?

Just to be clear, the development and maintainence of Firebug stopped several years ago. Mozilla introduced a new architecture for extensions called WebExtensions, which will be the only supported extension system once Firefox 57 is released. That means, Firebug as well as all other extensions

20 Oct 2017 10:56am GMT

Re: Firebug stopped recognizing the "! important"?

Note that Firebug is discontinued and unmaintained for several years now. Firebug users are advised to use the Firefox built-in DevTools. Those support the !important keyword (note: without space) within their Rules panel. Sebastian On Wednesday, October 4, 2017 at 2:19:06 PM UTC+2, Carlos

20 Oct 2017 10:39am GMT

Re: Firebug is not working in firefox 55.0.2 and below all versions.

Hi! You may have missed it, though Firebug is officially discontinued for several years now. Users are encouraged to use the Firefox built-in DevTools instead. Sebastian On Wednesday, October 4, 2017 at 2:17:04 PM UTC+2, ke...@cactusstudio.com wrote: > > > Hello Firefox Developers, > > Please

20 Oct 2017 8:18am GMT

18 Oct 2017

feedFirebug

Re: What is "Show chrome sources"?

fix it google On Friday, January 8, 2010 at 11:58:23 PM UTC+1, Steven Roussey wrote: > > What is "Show chrome sources"? I don't seem to see any difference with > the option on or off. >

18 Oct 2017 12:55pm GMT

16 Oct 2017

feedFirebug

Re: firebug html tab is empty after new firefox upadated

Firefox 56 is not compatible with Firebug. This is what I did to make it run again: - uninstall Firefox silent update service by running "C:\Program Files (x86)\Mozilla Maintenance Service\uninstall.exe" to prevent automatic Firefox updates - disable automatic updates from preferences: https://w

16 Oct 2017 11:42am GMT

Re: Firebug not comfortable Ubuntu Firefox 56.0 (64-bit)

Same issue here because the final version of firebug is 2.0.19 which is till firefox 54 now firefox is 56 so firebug is not compatible for this. On Friday, October 13, 2017 at 12:08:03 PM UTC+4, Bala Kumaran wrote: > > Hi, > > We have used Ubuntu Firefox 56.0 (64-bit) Browser it was recently >

16 Oct 2017 11:42am GMT

Re: Does Firebug not work any more in FF v56?

[image: Loudly Crying Face on Mozilla Firefox OS 2.5] El martes, 3 de octubre de 2017, 14:21:14 (UTC+2), Erik Krause escribió: > > Am 03.10.2017 um 12:48 schrieb Ben: > > Why does Firebug v2.0.19 not work any more? > > > > Is it because of Firefox v56? > > > > Is there a workaround/newer

16 Oct 2017 11:42am GMT

13 Oct 2017

feedFirebug

Re: [firebug] Re: firebug html tab is empty after new firefox upadated

On 2017-10-13, at 9:48 AM, Erik Krause wrote: > Am 07.10.2017 um 18:02 schrieb Adi: >> Same issue here, Firefox DEV tools sucks, i can't use it. > > This doesn't help anything. Please be more specific. Did you read the migration guide? > https://developer.mozilla.org/en-US/d

13 Oct 2017 9:58pm GMT

Re: firebug html tab is empty after new firefox upadated

This doesn't help anything. Please be more specific. Did you read the migration guide? https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug -- Erik Krause

13 Oct 2017 4:48pm GMT

27 Oct 2011

feedFirebug Working Group Google Group

Re: Firebug 1.9 beta

See examples on this page:
[link]

The message manager allows sending JSON based packets between chrome
and content processes. That's how Firebug needs to communicate with
the
current page instead of directly accessing it.

The message manager represents API we need from Gecko. This API is

27 Oct 2011 2:02pm GMT

Re: Firebug 1.9 beta

Yes, as soon as e10s replaced the current APIs. I'm aware of that.

Unfortunately the e10s page <[link]> is not
kept up-to-date. We need some specific API examples to be able to start
working on e10s.

So this means (at least for me) as long as the APIs are not existing and

27 Oct 2011 1:11pm GMT

Re: Firebug 1.9 beta

Sounds good

I'll postpone b1 and release a5 instead.

Please cc me on every new report that is blocking the beta.

Thanks!
Honza

27 Oct 2011 10:53am GMT

Re: Firebug 1.9 beta

A soon as e10s is in place Firebug just won't work -
no matter how many great features we have.

If we want to have working Firebug next year, we really need
to understand the importance of e10s and see the amount of work
needed to be done.

All new features we implement since now should support e10s,

27 Oct 2011 10:50am GMT

Re: [FWG] Re: Firebug 1.9 beta

Ah, that's right. Please create an issue for that, so we can keep track of
it.

Also for this you should create an issue including a test case.
Both of these are bugs and therefore could also be fixed in the beta
versions.

Would be great, if that could still be put into 1.9.

Great! Is it working based on the focus as I wrote in the enhancement

27 Oct 2011 10:04am GMT

Re: [FWG] Re: Firebug 1.9 beta

i see two regressions
- 'open with editor' isn't added to content area contextMenu,
not sure if we need to fix this, but fix is simple,
editorToContextMenu.js needs to be added to browser.xul
- after detaching firebug, searchbox panel focuses window where it
was opened first
just removing and adding searchbox fixes this, but i am not sure

27 Oct 2011 9:49am GMT

Re: Firebug 1.9 beta

I guess unfortunately not. And just for this we shouldn't move the release.

Remember 2874 <[link]> is just
a meta issue. It consists of smaller and larger issues. While the largest
ones could probably take a month to implement, the small ones are surely

27 Oct 2011 9:49am GMT

Re: Firebug 1.9 beta

On Oct 27, 12:52 am, Christoph Dorn <christ...@christophdorn.com>
wrote:
1-2 months? Depends of feedback (I am not getting much feedback during
alphas)

I have been working on AMD support for extensions issue 4718, it's now
working for my
HelloAMD example:
[link]

27 Oct 2011 8:55am GMT

Re: Firebug 1.9 beta

Would it help if we release a5 this week and b1 next week?

We have already discussed this, 2784 is huge and we just don't have
resources to implement that.

Here is what I think should be our priorities:
1) Fix memory leaks (and performance related issues)
2) Be ready for e10s (multiprocess)

27 Oct 2011 8:28am GMT

26 Oct 2011

feedFirebug Working Group Google Group

Re: [FWG] Firebug 1.9 beta

What is the ETA for 1.9 stable?
The only feature I would **really** love to have is the ability to dynamically register and unregister modules and panels. I have not checked lately where we are at with that. I can get up to speed next week and also look at the firebug logging and extensions for/via jetpack again to see if we can get that stuff working.

26 Oct 2011 10:52pm GMT

Re: Firebug 1.9 beta

Well, I guess I won't be able to finish issue 2916<[link]>nor
3071 <[link]> before then as
we discussed in the conf call of the 18th<[link]>this month. But they are just features, so they can be moved.

26 Oct 2011 10:29pm GMT

Firebug 1.9 beta

Firebug 1.9a4 seems to be in pretty good shape and so, we have been
discussing switching to beta phase. Since betas are uploaded on AMO,
we could also attract more beta testers and get more feedback.

Questions:

1) Do you agree that 1.9 beta 1 will be released this week on Friday?

2) Do you think there is an issue that should be fixed in 1.9?

26 Oct 2011 1:43pm GMT

21 Oct 2011

feedFirebug Working Group Google Group

Re: SVN -> getfirebug.com sync working

Yep, I got an email now, excellent!

Honza

21 Oct 2011 6:41am GMT

Re: SVN -> getfirebug.com sync working

Today it's also working for me again. The whole wiki was broken yesterday,
but Brian already fixed it now.
Sebastian

21 Oct 2011 6:12am GMT

Re: SVN -> getfirebug.com sync working

It seems to be working for me.

What specific page is broken for you?

Honza

21 Oct 2011 5:29am GMT