Mark D Hiatt wrote: (Q1) > How do you go about debugging a CSS? > > Are there any tricks you've picked up over the last several months or > years that seem to help you when what you meant isn't quite what you're > seeing? > (Q2) > One trick I've used quite a few times is to put a garish border around > whatever I'm working on at the moment. If my page is deep reds and browns, > I'll put a 1px solid yellow border around a DIV I am wrestling with, and > quite often that shows me that I'm having issues with margins or paddings > or whatever. > (Q3) > Along with that, one that has tripped me up quite a few times is the > automatic tag closer feature of Dreamweaver.
Q1. Firefox's DOM Inspector (Tools menu -> DOM Inspector - you might have to select it during a Custom install, can't remember) allows you to edit the CSS applying to a specific element on a page, including changing/removing/adding rules for a specific selector applied to a specific element. This can be invaluable. Microsoft have a (considerably inferior) developer toolbar in Beta test. Q2. Setting a border affects the box model - use the "outline" property instead, supported in FF1.5, Opera and Safari. Q3. Don't allow a supposedly useful tool to hinder your work - either disable such autocompletion features (probably possible, but I haven't looked at DW or its ilk in many years), or just switch to using a straightforward text editor. I always find such autocompletion features to be more trouble than they're worth. Your mileage may vary, of course. Cheers, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/ ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
