Almost two years ago I wrote a blog post about what I saw as problems in the IE9 developer tools.
Since then we’ve had IE10 released as well so I decided to revisit the post and see how have the development tools changed/improved since IE9.
- I made a point that when it comes to using
console.log(and the derivatives) you often found that you got
[object Object]. Well this is still the case, and most commonly you’ll see it if you’re using the console as a scratch pad to test things out. There are two solutions to this, one is to override the
console.logmethod in a similar was as I mentioned with “fixing” console.assert or alternatively override the
toStringmethod of your object, since the reason you get
[object Object]is because all it uses the
toStringmethod of the object (I override it to just do
- You still can’t clear the console without right-clicking or using
console.clear(), there’s a toolbar option that looks like it would do it but nope, that’s a cache clear button
- Related to the above point I really wish the Ctrl + R and/or F5 would work when input is focused on the dev tools, and by work I mean reload the page. Yes I get why they don’t work, the dev tools are running in a separate process, that’d be a nice thing to fix too…
- The list of provided User Agents is really good (as I said before) and the ability to save your own custom User Agents is nice
- Why is the DOM explorer still a static node list? C’mon this is 2013 guys and you make me refresh the DOM explorer when ever the DOM changes so I can inspect the current page state? Yes again I’m sure this is related to the fact that it’s a separate process but it’s just painful, especially if you’re working on a KnockoutJS UI or a SPA
- I would love an IndexedDB inspector like Chrome has in their dev tools, and since it’s build on ESE I would think that this shouldn’t be that big a deal, ESE is pretty well documented
The last few years has seen the IE team put in the hard yards to get IE back to being a highly competitive browser in the current market for users so I hope that they start focusing on making IE a competitive browser for the web developer.