On 23/07/2015 17:36, Panos Astithas 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?
I suggest chrome://devtools/content/debugger.xul if you are going to refactor devtools. Use case: SeaMonkey Phil -- Philip Chee <phi...@aleytys.pc.my>, <philip.c...@gmail.com> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
