On Thu, Jul 23, 2015 at 8:11 AM, Paul Rouget <p...@mozilla.com> wrote: > I guess by moving things to /devtools/, you also want to update the > URLs to chrome://devtools/content. > So then, we can compile and open the devtools with non-firefox builds > (thunderbird, b2g, seamonkey, ...). > But if the devtools include browser code, this won't work. For > example, we import > chrome://browser/content/utilityOverlay.js, which is Firefox only.
The main goal of this work is around making the DevTools codebase more approachable for contributors. We're not explicitly setting out to make reusing the front end easier from non-Firefox, but certainly moving out of /browser is one nudge in the right direction down that path. I'm guessing we'll still have some browser dependencies for the moment, but I'll take a look at this as I work on the file moves. - Ryan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
