Some Gaia developers don't use our developer tools. Let's make sure we fix the bugs that block them.

Some developers only work on device and almost never run Gaia on desktop, so bug 817580 is the most blocking one for them. Otherwise, an obvious painfull limitation when running Gaia in a Firefox tab is the lack of iframe selection support. When we open Gaia in a tab, the top level document is the system app, you will only see system app console messages and it is quite challenging to reach the current app window object to evaluate something against it. Also the inspector, debugger and style inspector are going to list all apps resources. That's a cool thing, as it allows you to target your app, but that's also painfull as you end up with very long list of resources. We can work around this in the gaia helper addon, but that may be something we want to make builtin into firefox. Is there a bug for iframe support?

> Otherwise, an obvious painfull limitation when running Gaia in a Firefox tab is the lack of iframe selection support. You mean, limiting the devtools to only one iframe? So we could imagine a way to lock the tools to one iframe, and forbid inner/outer-window inspection/debug/logs.

There is bug 784112 for the debugger, bug 609872 for the web console and possibly others for the other tools. I have explicitly added this as a discussion topic for the next work week. One parting thought: Gaia suffers a lot from this problem, due to the app == iframe design. However, I'm not so sure we would want to solve the generic issue of debugging, say a blog with embedded widgets, the same way as we want to treat debugging a Firefox OS device.

(In reply to Panos Astithas [:past] from comment #3) > One parting thought: Gaia suffers a lot from this problem, due to the app == > iframe design. However, I'm not so sure we would want to solve the generic > issue of debugging, say a blog with embedded widgets, the same way as we > want to treat debugging a Firefox OS device. +1. I tend to think there is common low level issues, like being able to switch the target of a given toolbox and handle iframes nicely in each tool. But we would most likely have a b2g specific behavior/ui via the gaia helper addon. I'll try to resurect my gaia branch that provide toolbox per app. That's dirty and not necessary the best way to go as it automagically show a toolbox for the foreground app. When you switch from one app to another you get a new toolbox. We end up loosing the toolbox for the system app.

I can't find `screenshot` button in 2/17 nightly, is it moved to else where?

Given changes in org priorities with Firefox OS, DevTools is unlikely to focus specifically on Gaia needs moving forward, so I believe it's time to close this meta-bug.