Sent by Ben Henick on 14 October 2005 19:07
On Fri, 14 Oct 2005 [EMAIL-REMOVED] wrote:
> I have head alot about DOM and DOM inspectors. I have also played
> around with Fire Fox and looked throughout the DOM interface, but I am
> still not qute sure of the benefit of it and if it has anything to do
> with CSS although I can see the sructuring of it.
....Which is most of the point. With the DOM Inspector ONE can easily
notice unneeded containers and discern which style rules are being applied
to each element, in the event that something is being unexpectedly
inherited (or not).
There's another extension that integrates Tidy into source view, and for
me that's just as big a lifesaver (as it allows me to identify unclosed
elements that are b0rking my styles).
What DOM is meant for is to provide a structural representation of a
document, so that elements can be manipulated via scripting API's... but
its application to styling should be fairly obvious if you work much with
descendant selectors.
HTH
--
Ben Henick "In the long run, men hit only what they aim
Sitebuilder At-Large at. Therefore, though they should fail
http://www.henick.net/ immediately, they had better aim high."
[EMAIL-REMOVED] -- Henry David Thoreau
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
