Closed Bug 1047248 Opened 10 years ago Closed 8 years ago

[e10s] Firebug 2.0 does not work with e10s. (FYI: Use Firebug 3 instead; Firebug 3 will support e10s.)

Categories

(Firefox :: Extension Compatibility, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
e10s + ---

People

(Reporter: sebo, Unassigned)

References

Details

(Keywords: addon-compat, meta)

Several panels of Firebug 2.0.2 don't work when e10s is enabled and it crashes the page when it's opened.

This is mainly meant to be a tracking bug as the Firebug Working Group decided to merge Firebug with the built-in devtools. I.e. Firebug is recreated from scratch based on the devtools and extending them.
So e10s compatibility is just required for the extensions to the devtools and will be mainly coordinated with the devtools team.

Sebastian
Blocks: dte10s
Mentor: cpeterson
tracking-e10s: --- → +
Depends on: 1047558, 1047587
Keywords: meta
No action, when clicking the FireBug icon in the menu
Do you refer to Firebug running on an e10s enabled profile?

Sebastian
Depends on: 1084054
https://blog.getfirebug.com/2014/11/10/firebug-3-next-generation-of-firebug/

What should be the status of this bug now?

Florent
(In reply to fayolle-florent from comment #3)
> https://blog.getfirebug.com/2014/11/10/firebug-3-next-generation-of-firebug/
To summarize the blog post: The upcoming Firebug version (currently in alpha phase) supports e10s. The current Firebug 2.0.6 now displays a message on e10s enabled profiles pointing to the new version.

Sebastian
Flags: needinfo?(cpeterson)
Thanks, Sebastian. We can probably close this bug now.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(cpeterson)
Resolution: --- → FIXED
Summary: [e10s] Firebug does not work with e10s → [e10s] Firebug 2.0 does not work with e10s. (FYI: Use Firebug 3 instead; Firebug 3 will support e10s.)
Assignee: :tracy
Link to add-on: https://addons.mozilla.org/en-US/firefox/addon/firebug/?src=search
Contact info for add-on: http://getfirebug.com/
Bug #: this bug 1047248
Add-on ID: firebug@software.joehewitt.com
How well does it work?: 100%
SDK-based: restartless addon
Chromium version: no
Hi Sebastion - I'm working to figure out how all the most widely adopted add-ons are doing with e10s.  It says version 3.0 works, but i see only 2.0.17 available?  Do you have plans on releasing 3.0?  Or has 2.0.17 hit e10s compatibility?  We have folks that can test it out on different platforms if you think it is - but I don't want them to test if we know it's not.
Status: RESOLVED → REOPENED
Flags: needinfo?(sescalante)
Flags: needinfo?(sebastianzartner)
Resolution: FIXED → ---
As stated in the Firebug blog[1] Firebug.next (aka Firebug 3.0) is shipping built-in with Firefox as a theme for the Firefox DevTools (against the blog post already in version 48.0). Development on it as a separate add-on is abandoned.

Having said that, I left the Firebug Working Group some time ago. The person to contact for any further questions is Jan 'Honza' Odvarko, but I guess I can savely close this again.

Sebastian

[1] https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/
Status: REOPENED → RESOLVED
Closed: 10 years ago8 years ago
Flags: needinfo?(sescalante)
Flags: needinfo?(sebastianzartner)
Resolution: --- → FIXED
(In reply to Sebastian Zartner [:sebo] from comment #9)
> As stated in the Firebug blog[1] Firebug.next (aka Firebug 3.0) is shipping
> built-in with Firefox as a theme for the Firefox DevTools (against the blog
> post already in version 48.0). Development on it as a separate add-on is
> abandoned.
> 
> Having said that, I left the Firebug Working Group some time ago. The person
> to contact for any further questions is Jan 'Honza' Odvarko, but I guess I
> can savely close this again.
> 
> Sebastian
> 
> [1] https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/

thank you!! sorry - i didn't interpret the blog right (did try there first - but looking specifically for 3.0).  that's great news and thank you!
You need to log in before you can comment on or make changes to this bug.