On Dec 20, 2007 8:23 AM, Matt Palmer <[EMAIL PROTECTED]> wrote: > On Wed, Dec 19, 2007 at 10:36:11PM +1100, Ian Wienand wrote: > > Does anyone have any debugging tips for this sort of thing? My > > current technique consists mostly of guessing what should be > > happening! > > Firebug is apparently the gold standard, but I've never used it (one day I > will!). I use the Web Developers Toolbar (another Firefox extension) > which > has this nifty "View Style Information" command (Ctrl-Shift-Y) -- you just > click on anything and the CSS styles that apply to that element get > displayed in a separate window, in precedence order. You just read them > going down the page, and last specification of a particular attribute > wins, > so to speak. > > I'd imagine Firebug probably has that option as well, so don't take my > recommendation over that of the rest of the web-hacking community. > Firebug > does seem to be the winner, based on size of noisy userbase. >
Indeed Firebug does have the same option, but it goes further. In Firebug you can also add/edit/delete any CSS property, as well as temporarily disable them (very useful for debugging!). It also ties in with a DOM browser/editor (side-by-side), which is handy for dealing with complex layouts. I usually keep the Web Developer's Toolbar around as well though, because it does have a few nifty features that Firebug doesn't. - Michael
_______________________________________________ coders mailing list [email protected] http://lists.slug.org.au/listinfo/coders
