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.
On Thu, Jul 23, 2015 at 11:36 AM, Panos Astithas <p...@mozilla.com> wrote: > On Thu, Jul 23, 2015 at 8:25 AM, Paul Rouget <p...@mozilla.com> wrote: >> >> On Wed, Jul 22, 2015 at 2:48 PM, Panos Astithas <p...@mozilla.com> wrote: >> > If you are thinking about shipping them as part of browser.html, we >> > still >> > have XUL dependencies that we need to get rid of first and that work is >> > independent from moving the code to a top-level devtools/ directory. >> >> We don't use XUL, but we can still open XUL windows. >> Would it be possible to use the devtools without chrome://browser/ >> being accessible? > > > I doubt it, although, to be honest, I am not entirely sure. We already use > paths like chrome://browser/content/devtools/debugger.xul in the code, so > they would have to be changed first. Would using resource: URLs work better > for browser.html? > -- Paul _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
