There is big difference between Firebug and Firebug Lite

Firebug Lite is a bookmarklet, pure web app running inside the page content - 
together with the App it’s debugging. There is no need to cross any process 
boundaries when inspecting app’s objects. Btw. the disadvantage of Firebug Lite 
is that it doesn’t have any extra privileges and that’s e.g. why it doesn’t 
have a debugger or net panel.

Firebug is Firefox add-on, running in ‘chrome’ scope, not inside the page. This 
scope gives Firebug extra power and it can access all Firefox API (at least 
those available for JS) and implement many powerful features like Debugger and 
Net panels. But, it needs to access the app (i.e. the page, the debuggee) 
somehow from outside. It’s been easy in non-multiprocess environment since 
Firebug could use direct reference to app’s objects living inside the page. 
It’s different in multiprocess browser since the app is running in different 
process than Firebug (the chrome scope).

The communication between chrome and content (the page) is harder now (e.g. it 
needs to use an async protocol) and Firebug is not ready to do that. This would 
involve a lot of code refactoring (most of it). There are no resources neither 
motivation to do that. Sorry.

The right thing to do here is to switch to built-in Firefox DevTools. If there 
is something you miss, please file a bug in bug here:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools

We are working hard to fix those.

Honza



> On 27 Apr 2016, at 09:03, Prakash Chokalingam <prak...@freshdesk.com> wrote:
> 
> Please enable firebug for multi proccess enabled firefox developer edition,It 
> will be very usefull.Already firebug lite working fine in the multi proccess 
> browser chrome.
> 
> -- 
> 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+unsubscr...@googlegroups.com 
> <mailto:firebug+unsubscr...@googlegroups.com>.
> To post to this group, send email to firebug@googlegroups.com 
> <mailto:firebug@googlegroups.com>.
> Visit this group at https://groups.google.com/group/firebug 
> <https://groups.google.com/group/firebug>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/firebug/426e28d8-b103-4626-b246-4b21853f6084%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/firebug/426e28d8-b103-4626-b246-4b21853f6084%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to firebug@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/5BA27FF1-24D4-48C7-A72A-AAA4A97409AF%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to