Originally Posted by complete
Do you use firebug and run your page through your localhost?
I use Firefox. Ctrl+Shift+K brings up the error console, Ctrl+Shift+I brings up the generated DOM, and Ctrl+Shift+Q lets you monitor the network. Firefox also has a font inspector.
I also use XAMPP to test files locally, which saves time over constantly uploading the files to a live server.
Originally Posted by glenngv
I also don't like IE dev tools very much but the upcoming IE11 dev tools look very good and maybe even better than Chrome and Firebug.
I have IE11/Windows 8.1 Developer Preview installed. While the tools are a big improvement over IE10, they have some drawbacks. In particular:
- The console still only records errors after it's opened and you refresh the page.
- The console reports useless things like indicating that an XSLT transformation occurred.
- Microsoft removed the compatibility modes switcher for older versions of IE, which, while not entirely accurate, were quicker to use than booting up a virtual machine (which could always be done at the end for further bugfixing). There's a mode field in the options that reflects the state of the document, but you can't change the value.
- It still uses F12 key activation, which is annoying because I have to physically look at my keyboard every time I need to use it. I can find shortcuts in Firefox and Chrome (Ctrl+Shift+I/J) without even looking at the keyboard. But that's just a personal thing, I guess.
On the other hand:
- You can have the console up while any other developer pane is open, which I don't think any other browser has out of the box.
- The UI is large and readable, which I assume is for touch compatibility.
- It also has a better Trace tool than Chrome when it comes to determining the font in use. (But Firefox is still better.)