As far as I know, developer tools are only for Firefox (and SeaMonkey?). However they exist in omni.ja for xulrunner: 14283 01-01-2010 00:00 chrome/toolkit/content/global/devtools/dbg-browser-actors.js 39581 01-01-2010 00:00 chrome/toolkit/content/global/devtools/dbg-script-actors.js 6545 01-01-2010 00:00 chrome/toolkit/content/global/devtools/dbg-transport.js 13623 01-01-2010 00:00 modules/devtools/dbg-server.jsm 29914 01-01-2010 00:00 modules/devtools/dbg-client.jsm 17196 01-01-2010 00:00 jsloader/resource/gre/modules/devtools/dbg-server.jsm 34428 01-01-2010 00:00 jsloader/resource/gre/modules/devtools/dbg-client.jsm And dbg-transport.js also exists in dist/xulrunner: jssubloader/185/resource/gre/chrome/toolkit/content/global/devtools/dbg-transport.js
(In reply to Takanori MATSUURA from comment #0) > And dbg-transport.js also exists in dist/xulrunner: > jssubloader/185/resource/gre/chrome/toolkit/content/global/devtools/dbg- > transport.js This part has been already filed as bug 732649. So in this bug, I'd like to focus on the issue that debugger files are bundled with xulrunner.
The part of the script debugger that resides in toolkit/ is a general-purpose remote debugging protocol implementation. It can be used to provide the foundation for debugging, testing and inspecting xulrunner-based applications. In that sense, I don't think it's inappropriate to include it with xulrunner builds. The UI part that is specifically tailored to firefox is located in browser/ and of course is not bundled with xulruner.
Example code to interact with the remote protocol can be found here: https://wiki.mozilla.org/Debugger_Client_API
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.