3 ms·
Safari's Web Inspector is far, far better than it used to be, and has indeed gone a long way towards catching Firebug. The problem is that it isn't there yet; o
by ionfish 17y ago
Safari's Web Inspector is far, far better than it used to be, and has indeed gone a long way towards catching Firebug. The problem is that it isn't there yet; otherwise, I'd only be dipping into Firefox to test things.
The Web Inspector's major shortcoming is the lack of a UI to edit the some aspects of the DOM directly (you can do it in the JS console by running DOM queries). One can't remove existing nodes or add new ones via the Web Inspector UI; nor can one add new CSS styles (although one can edit node attributes and the values of existing CSS declarations).
All of this means that even for those of us with access to Safari (i.e. not developers working on Linux) there's still a pressing need for Firebug, so if they keep breaking it with updates pretty soon everyone will be reverting to 3.0.x and the older versions which, while they had a few niggles, essentially worked.
- dflock 17y agoI'm a web developer running Linux exclusively and I've recently started using Chromium, which works great and provides the webkit Web Inspector (right click, Inspect Element). Inspector isn't quite as good as Firebug, but Chromium is quite a bit better than Firefox, so it's not a bad trade.
- msmithstubbs 17y agoWeb Inspector does allow you to create new CSS rules, though it's not intuitive at all. When editing an existing rule you can add a new rule on the same line.Once you hit enter Web Inspector will put the new rule on a new line. If there is no existing rule for an element you can cheat one in by adding 1 pixel padding via the metrics panel, which creates in inline padding style. The edit that rules or and add new rules as above. Again, not as good as Firebug, but might be useful for some. It looks like this is being actively worked on: https://bugs.webkit.org/show_bug.cgi?id=18224 https://bugs.webkit.org/show_bug.cgi?id=18224 I agree the lack of DOM editing UI is a problem.