It is currently not possible to debug and inspect app pages launched by MozActivities in the App Manager

You should be able to debug them once bug 977043 is fixed.

Looks like this is working now :)

Something broke, no longer working :(

(In reply to Amir Nissim (:amirn) from comment #3) > Something broke, no longer working :( I don't think it was working before. Can you describe exactly what you do?

Still not working for me too. My testing project is quite simple: A manifest saying to open a page (which is not the index) when a WebActivity is fired. The debugger still debug the index page, which is not a bad idea since the index page is still open, but I think it should add a new tab for the other page.

As highlighted in a recent duplicate, bug 1123584, it is now ~possible~ to debug activities, it is going to be even more *possible* once bug 1055452 lands (your activity won't be overloaded by index.html when connecting to the activity app). But it is still unclear: 1/ First, above all, it requires to toggle a custom setting hidden in toolbox configuration panel. "Select an iframe as the currently targeted document". 2/ Then, you have to have a very good understanding of activites in order to connect to the related process of the activity 3/ Finally, you have to be aware of the iframe switching feature in toolboxes in order to switch to the activity document. Ideally, there would be no magic setting to toggle and activities would appear explicitely in WebIDE interfaces. Let figure out in this bug how to do that! Alive, your proposal about adding data-xxxx attributes on iframes may help, but I wish we could find some more standard ways of sorting frames...

(In reply to Alexandre Poirot [:ochameau] from comment #8) > As highlighted in a recent duplicate, bug 1123584, it is now ~possible~ to > debug activities, it is going to be even more *possible* once bug 1055452 > lands (your activity won't be overloaded by index.html when connecting to > the activity app). > > But it is still unclear: > 1/ First, above all, it requires to toggle a custom setting hidden in > toolbox configuration panel. "Select an iframe as the currently targeted > document". > 2/ Then, you have to have a very good understanding of activites in order to > connect to the related process of the activity > 3/ Finally, you have to be aware of the iframe switching feature in > toolboxes in order to switch to the activity document. > > Ideally, there would be no magic setting to toggle and activities would > appear explicitely in WebIDE interfaces. > Let figure out in this bug how to do that! > > Alive, your proposal about adding data-xxxx attributes on iframes may help, > but I wish we could find some more standard ways of sorting frames... Does desktop firefox has the information of opened tabs' relationship? How does it know? For example, I remember there is an addon to help you to group the tabs by its opener. 1. google.com -> abcde.com -> ... 2. www.facebook.com -> opened-by-facebook.com -> further-opened.com... 3. www.mozilla.com -> mdn.org -> .... i.e., if there is a standard way to identify the relationship of tab(window) let's get it.

Apps are being removed.