An early prototype of the Inspector even included a significant portion of Firebug. We thought long and hard about including Firebug wholesale and considered several approaches to integrating it. We had ambitious platform changes planned: The JSD API that Firebug uses to debug Javascript had aged badly, and we wanted to co-evolve the tools alongside a new Spidermonkey Debugger API. Baking them into the browser let us take advantage of the existing Mozilla community and infrastructure, and building in mozilla-central makes a huge difference when working with Gecko and Spidermonkey developers. It introduced the world to visual highlighting of the DOM, inplace editing of styles, and the console API.īefore the release of Firefox 4 we decided that Firefox needed a set of high-quality built-in tools. For a long time, Firebug was the best game in town. If you have a Firefox OS device running the latest 1.2 nightlies, you can connect the tools directly to the phone. Install the Firefox OS Simulator to see how your app will behave on a device. The list goes on, and you can read more about recent developments in our series of Aurora Posts.Īfter getting to know the tools, start the App Manager. The network monitor helps you debug your network activity. The inspector has paint flashing, a new font panel, and a greatly improved style inspector with tab completion and pseudo-elements.
Source maps let you debug source generated by transpilers or minimizers. The tools have improved a lot lately: black-boxing lets you treat sources as system libraries that won’t distract your debugging flow. Grab the latest Aurora browser, and start up the tools from the Web Developer menu (a submenu of Tools on some platforms). If you haven’t tried the Firefox Developer Tools in the last 6 months, you owe it to yourself to take another look.
0 kommentar(er)
