Comments on: Web Inspector Vs. Firebug

By: C.Shamis

C.Shamis — Thu, 07 Oct 2010 00:32:05 +0000

Nor does Web Inspector offer any way to view XHR POST data. How in the heck are you supposed to debug AJAX calls when you can’t see what’s getting passed back and forth?
Some well meaning (but hopelessly misguided) people have suggested using Wireshark to parse the packets.

Well… if I was willing to go to the trouble of using a packet sniffer to see the conversation, I wouldn’t exactly need Web Inspector in the first place now would I?

So, why bother having it? It doesn’t do anything useful at all.

By: Yair

Yair — Tue, 07 Sep 2010 06:21:31 +0000

Hi,
Nice and interesting post.
I’ll add to this 2 things that prevent me from using Web Inspector:
1. You can’t add properties to a css rule on the fly. In Firebug, you can easily right-click inside the area of any css rule and choose “new property”. I found no such option in Web Inspector.
2. When adding/editing css properties, you can start typing the property name, and firebug will auto-complete it. Using the up and down arrow key will browse through all the possible values that start with the letters that you typed. The same is true for the properties values; using the up and down arrow keys will browse through all the possible values for that css property. That saves you the need to remember the exact syntax and to go to the W3 documentation all the time.

These two things alone renders Web Inspector quite useless to me , as these are features I use heavily on a daily basis.

– Yair

By: links for 2010-03-02 « that dismal science

links for 2010-03-02 « that dismal science — Tue, 02 Mar 2010 19:33:20 +0000

[...] Web Inspector Vs. Firebug · Jay Robinson (tags: design webdev css html browser firefox debugging firebug safari) [...]

By: Web Inspector Vs. Firebug

Web Inspector Vs. Firebug — Mon, 01 Mar 2010 19:10:29 +0000

[...] full post on Hacker News If you enjoyed this article, please consider sharing it! Tagged with: Firebug [...]