Firebug not found when I install Firefox 55.0.2

266 views
Skip to first unread message

Jorge Luis Callalle Torres

unread,
Aug 19, 2017, 1:56:45 PM8/19/17
to Firebug
Firebug not found when I install Firefox 55.0.2
WHY ?????????????????

Michael

unread,
Aug 19, 2017, 4:17:06 PM8/19/17
to fir...@googlegroups.com
Firebug is no longer compatible with Firefox.

More specifically, Firebug is not compatible with multiprocess firefox. If you need it, you can use Firefox ESR, which has multiprocess disabled by default, and maintains Firebug functionality.

NB: Firefox developer tools is not an acceptable substitute. Far too often, it will refuse to show anything in the CSS of a webpage -- it insists that there are no CSS rules in effect at all.

On 2017-08-18, at 1:15 PM, Jorge Luis Callalle Torres <jlcal...@gmail.com> wrote:

Firebug not found when I install Firefox 55.0.2
WHY ?????????????????

--
You received this message because you are subscribed to the Google Groups "Firebug" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
To post to this group, send email to fir...@googlegroups.com.
Visit this group at https://groups.google.com/group/firebug.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/5a882eb7-ee34-4412-a8f8-d74ab5f00cd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

---
Entertaining minecraft videos

Sebastian Zartner

unread,
Aug 19, 2017, 7:17:32 PM8/19/17
to Firebug
On Saturday, August 19, 2017 at 10:17:06 PM UTC+2, Michael_google gmail_Gersten wrote:
Firebug is no longer compatible with Firefox.

More specifically, Firebug is not compatible with multiprocess firefox. If you need it, you can use Firefox ESR, which has multiprocess disabled by default, and maintains Firebug functionality.

Note that with Firefox 57 (and 59 ESR) Firebug (as well as most other current extensions) will definitely stop working, as at that point Firefox will only support WebExtensions. Though that also means that Firefox will (actually already does) support extensions which were initially written for other browsers.

NB: Firefox developer tools is not an acceptable substitute. Far too often, it will refuse to show anything in the CSS of a webpage -- it insists that there are no CSS rules in effect at all.

This sounds like a bug, which I didn't experience so far. If you can break this down to a simple test case, you should file a bug report for that. Please CC me when you do so, so I can follow it.

Sebastian

Michael

unread,
Aug 19, 2017, 9:32:28 PM8/19/17
to fir...@googlegroups.com

On 2017-08-19, at 4:17 PM, Sebastian Zartner <sebastia...@gmail.com> wrote:
>
> > NB: Firefox developer tools is not an acceptable substitute. Far too often, it will refuse to show anything in the CSS of a webpage -- it insists that there are no CSS rules in effect at all.
>
> This sounds like a bug, which I didn't experience so far. If you can break this down to a simple test case, you should file a bug report for that. Please CC me when you do so, so I can follow it.

Simple test case? So far, it's random -- about 70% of the time. Yes, it's very common for me, but it also goes away with a restart, and shows up from an unknown trigger.

Erik Krause

unread,
Aug 20, 2017, 7:19:31 AM8/20/17
to fir...@googlegroups.com
Am 20.08.2017 um 03:32 schrieb Michael:
>>> NB: Firefox developer tools is not an acceptable substitute. Far
>>> too often, it will refuse to show anything in the CSS of a
>>> webpage -- it insists that there are no CSS rules in effect at
>>> all.

>> This sounds like a bug, which I didn't experience so far. If you
>> can break this down to a simple test case, you should file a bug
>> report for that. Please CC me when you do so, so I can follow it.

> Simple test case? So far, it's random -- about 70% of the time. Yes,
> it's very common for me, but it also goes away with a restart, and
> shows up from an unknown trigger.

Never experienced anything like that. Could it have to do with another
extension? Did you try in a fresh FF profile?

--
Erik Krause

Michael

unread,
Aug 21, 2017, 1:05:04 PM8/21/17
to fir...@googlegroups.com
Did not consider other extensions. Did not try a fresh profile.

As far as I know, only Firebug prevents starting up in multi-process mode, so I figured none of the others would cause problems.

>
> --
> Erik Krause
>
> --
> You received this message because you are subscribed to the Google Groups "Firebug" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to firebug+u...@googlegroups.com.
> To post to this group, send email to fir...@googlegroups.com.
> Visit this group at https://groups.google.com/group/firebug.
> To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/d1aa4b79-f16a-9a84-1952-50a80c00772e%40gmx.de.
> For more options, visit https://groups.google.com/d/optout.

Sebastian Zartner

unread,
Aug 21, 2017, 5:13:14 PM8/21/17
to Firebug
On Monday, August 21, 2017 at 7:05:04 PM UTC+2, Michael_google gmail_Gersten wrote:

On 2017-08-20, at 4:19 AM, Erik Krause <erik....@gmx.de> wrote:

> Am 20.08.2017 um 03:32 schrieb Michael:
>>>> NB: Firefox developer tools is not an acceptable substitute. Far
>>>> too often, it will refuse to show anything in the CSS of a
>>>> webpage -- it insists that there are no CSS rules in effect at
>>>> all.
>
>>> This sounds like a bug, which I didn't experience so far. If you
>>> can break this down to a simple test case, you should file a bug
>>> report for that. Please CC me when you do so, so I can follow it.
>
>> Simple test case? So far, it's random -- about 70% of the time. Yes,
>> it's very common for me, but it also goes away with a restart, and
>> shows up from an unknown trigger.
>
> Never experienced anything like that. Could it have to do with another extension? Did you try in a fresh FF profile?

Did not consider other extensions. Did not try a fresh profile.

Instread of a new profile, you may start your normal profile in safe mode, which deactivates the add-ons temporarily. To do so go to about:support, click the Restart with Add-ons Disabled... and follow the instructions.

As far as I know, only Firebug prevents starting up in multi-process mode, so I figured none of the others would cause problems.

There are other extensions not working in multi-process mode, but this issue may be unrelated to that mode.

While we've discussed this issue here now, I want to note that we've hijacked Jorge's thread about why Firebug doesn't work in Firefox 55. Furthermore, this issue should better be discussed in the channels of the Firefox DevTools team, so they can provide help.

Sebastian

Lý Thành Phúc

unread,
Sep 1, 2017, 8:22:20 AM9/1/17
to Firebug
Bạn có thể cài Firebug từ tập tin .xpi

https://youtu.be/JzTQ1yCkjMQ
Reply all
Reply to author
Forward
0 new messages