Jord:

Thanks for the info. I'm just kind of curious though being relatively
new to Dreamweaver and CSS. Why doesn't Dreamweaver display some CSS
combinations in Design view? I always preview everything and test
everything in various browsers, but when I'm designing a page in
Dreamweaver it's a real pain to not be able to see something as I'm
designing it. To have to go back and forth to preview in a browser to
see what I've just coded and if it looks OK can be very time consuming.
After all, that's the reason to use a WYSIWYG editor such as
Dreamweaver, right? Do you (or anyone else) think this will be
"corrected" in future updates of Dreamweaver, or is there some
limitation which makes it impossible for Dreamweaver to display certain
CSS items properly? And what determines what CSS Dreamweaver can
display and what it cannot? Hey, maybe more questions than you care to
address, but maybe someone on the list has some insight. Thanks again.

Steve



> Subject: Re: First-Child Pseudo-Class
> From: "Jordan L. Chilcott - Dreamweaver Talk List Admin"
> <dreamweaver-admin@blueworld.com>
> Date: Fri, 3 Jan 2003 14:47:08 -0500
>
> DWMX doesn't display every possible combination of CSS available. There
> are many things that it won't display. Thus, it is always best to test
> your CSS handiwork using a handful of browsers. Then again, that is
> where one should be putting their pages to the test. :-)
>
> jord


------------------------------------------------------------------------
List Administrator: <mailto:dreamweaver-admin@blueworld.com>
To Unsubscribe: <mailto:dreamweaver-off@blueworld.com>
Archives: <http://www.listsearch.com/dreamweavertalk.lasso>