John,
When you write code, you mean CSS + HTML code only? If not, there are tests
that can verify if it works as intended. If so:
1) Validators
This should do for semantic errors or typos.
2) Version control system
If you use one, revert to previous revision. Is your error there? Yes ->
check changes between this and next revision - there's problem root. No ->
go back one more revision.
Most VCS's comes with some sort of diff tool. If you're on *nix systems,
you have diff command.
3) Version control... manually
Delete part of your changes. Is your error there? Yes -> check what you've
deleted, there's your problem. No -> revert next change you made ("go back
one more revision" step).
4) Debugging
Launch Firebug and apply your changes from "bad" CSS on your site,
overriding "good CSS". Effects should be visible live. This is also manual
testing, to be honest. Also, if you don't have many rules from different
sources, you may want to check CSS Usage add-on to Firebug - it displays
rules used in green, unused in red. If styles don't work occasionally it's
because they can't be applied - then they'll be red. If they work, but not
as they should, they'll be green.
pozdrawiam,
Tomasz Borek
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
