When the Firefox e10 is enabled, the HTML menu in Firebug disappears.

72 views
Skip to first unread message

Aleš Ulrych

unread,
May 3, 2017, 7:55:59 AM5/3/17
to Firebug
Hello,
I have a problem. When I have Electrolysis (e10) turned on in Firefox,
The HTML menu in Firebug I'm actively using will disappear. I did not come up with it,
How to turn it back on when electrolysis is turned on.

Auto Generated Inline Image 1

Aleš Ulrych

unread,
May 3, 2017, 8:47:53 AM5/3/17
to Firebug
Here is Firebug with disabled e10s


Dne středa 3. května 2017 13:55:59 UTC+2 Aleš Ulrych napsal(a):
Auto Generated Inline Image 1

Sebastian Zartner

unread,
May 3, 2017, 4:47:11 PM5/3/17
to Firebug
When e10s is enabled, the Firefox DevTools are opened instead of Firebug, because Firebug does not work with e10s. Those tools have the HTML ancestor path is at the bottom of the panel.

Sebastian

Aleš Ulrych

unread,
May 4, 2017, 5:16:11 AM5/4/17
to Firebug
Thanks for the info, I thought it was just some cut Firebug. I also use Firebug as a helper for translating a German web-based e-shop when I receive an HTML code. Just leave me a blank page open in Firefox, turn on Firebug, choose to edit and insert HTML code there, and right now in Firefox I can see what it contains (bullets, tables, headings ... including properly translated HTML entities). I have an overview and very easy to translate. Then I copy the HTML code and return it back to the customer. With Firefox Devtools, I have no option to edit the HTML code to make it look the same as Firebug. The only solution for me is to turn off the E10s yet. :(
Is support planned?


Dne středa 3. května 2017 22:47:11 UTC+2 Sebastian Zartner napsal(a):

Sebastian Zartner

unread,
May 4, 2017, 7:24:45 AM5/4/17
to Firebug
Within the Firefox DevTools you have similar options to edit the HTML. You can edit attributes and text contents (and even tag names, which was not possible in Firebug) by double-clicking them. To edit the whole HTML structure under a specific element, right-click the element and choose Edit As HTML from the context menu. The only thing that's not yet working is the live update of the website while typing, which is reported as bug 1067318 and bug 815464.

Note that I have written a migration guide explaining the most common questions for Firebug users. Please let me know if you're missing something there. Furthermore, there is a bug report covering all Firebug features that are currently missing in the DevTools. If you're missing something that's not yet filed blocking that one (see the list under "Depends on"), please file it and mark it as blocking bug 991806.

Last but not least, I want to note that while the DevTools are still missing some (important) features of Firebug and their UI is not as good as Firebug's, they are in some areas already far more powerful than Firebug. E.g. they have an Animations Editor, they allow you to filter the CSS properties, they have a color picker and different other CSS property helpers, and they allow to inspect the fonts used within an element, to name just a few of their features.

Sebastian
Message has been deleted

Aleš Ulrych

unread,
May 4, 2017, 8:04:53 AM5/4/17
to Firebug
Thanks for the instructions, it took me a moment to understand how it works now. However, I have to say that Firebug seems better to me. I very much miss the fact that when I edit (translate) HTML, Devtools does not show me immediate changes in the browser, as Firebug does. I always have to finish the edits, check them and then turn them on again, which makes me very reluctant. This could definitely improve. Meanwhile, I will stay with Firebug and Devtools will try out some other version.

Dne čtvrtek 4. května 2017 13:24:45 UTC+2 Sebastian Zartner napsal(a):

Aleš Ulrych

unread,
May 4, 2017, 8:09:09 AM5/4/17
to Firebug
I'm sorry, I see you've already written about the live update. I will read your instructions. Thanks for the help.

Dne čtvrtek 4. května 2017 14:04:53 UTC+2 Aleš Ulrych napsal(a):

Sebastian Zartner

unread,
May 4, 2017, 8:44:33 AM5/4/17
to Firebug
Note that the live update issue is marked as one of the most important Firebug gaps.

Sebastian
Reply all
Reply to author
Forward
0 new messages