Web console is one of the actors that doesn't use sdk modules. It faces the global scope sharing issue where dependencies of one file is randomly defined in another one. It will also help switching to lazy loading actor, only implemented for actors defined as modules (bug 988237). And it is also a dependency of bug 859372 work.

https://tbpl.mozilla.org/?tree=Try&rev=a268f75f972d Quite straightforward. The only thing that questioned me is the hasNativeConsole thing, I remember that I already did that (copy paste it) and I got r- from Panos. As I don't really know what is the best option, I kept it as-is. But we can't make webbrowser depend on webconsole as it would defeat lazy loading of actors by forcing to load the console even if you don't open the console panel. (as hasNativeConsole is called as soon as you attach to a tab)

Previous try run failed because I was using LongStringActor from string.js instead of using the one from script.js...

Comment on attachment 8408193 [details] [diff] [review] patch https://tbpl.mozilla.org/?tree=Try&rev=ba8eb1f24f80

Comment on attachment 8408193 [details] [diff] [review] patch Review of attachment 8408193 [details] [diff] [review]: ----------------------------------------------------------------- /me likes!

backed this out from m-c (and also in the next merge from the other integrations trees) too, for request from Alexandre, since this seems has caused regressions

http://hg.mozilla.org/mozilla-central/rev/99d367b1adb2 The patch broke on-device debugging (bug 998898) and browser toolbox (bug 998912). I prefer to back it out and take some time to reland a patch that doesn't break stuff.

This time I tested on device and the browser toolbox. It appears that I got tricked by the "multiple main.js" for the browser toolbox breakage. We shouldn't pull DebuggerServer from dbg-server.jsm, which always retrieve the shared one for tabs. Instead we can pull it from require("devtools/server/main"), which will eventually return the expected one in browser toolbox scenario. I also broke b2g in previous patch. That time it was more obvious. It was because of `devtools` symbols, previously defined in the "magic shared global scope" by webconsole.js and used by webbrowser.js... In this patch I'm only documenting the "magic shared global scope" for webbrowser, as this isn't the goal of this bug to address webbrowser issues. Eddy will most likely address that in bug 859372.

Comment on attachment 8410371 [details] [diff] [review] patch https://tbpl.mozilla.org/?tree=Try&rev=ede13003a4fa

Comment on attachment 8410371 [details] [diff] [review] patch Review of attachment 8410371 [details] [diff] [review]: ----------------------------------------------------------------- This looks good to me. I've tested the browser toolbox case here too, seems fine now. May need to rebase though, for me it conflicts with your patch from bug 997239.

rebased.