Someone has just ask me why his webpage look awful in Mozilla (thanks to his old-school table layout filled with images that replace text). I did solved his problem (setting padding to zero). But how sad…

If people want to have pixel-perfect website, I’d rather want them to make Flash instead… Although Flash is never a good thing to accessibility and maintenance, I think it is far better than the ugly codes generated by Dreamweaver…

I’m pretty strongly in favor of making pages that validate. If Dreamweaver produces invalid HTML, then that sounds like a bug to me, and Macromedia should fix it. Especially since WaSP helped Macromedia clean up Dreamweaver MX’s output.

Using CSS to do all of the formatting, however, has turned out to be a royal pain. I chose to do it on my weblog because it sounded like a good idea. A year later, I wonder what the point is. It has caused me a lot of grief, and in return has given me… nothing. My weblog software already separated content and presentation: the content is in the database, and the PHP pages defined the presentation.

i am trying to code webpage with total css compatibility, but it’s not that easy. i applaud your grit and ability to do that. i do see the advantage and the long term survival of webpages using web standards.

dreamweaver is not entirely bad software, i use it to cleverly interchange between html code and WYSIWYG environment, not that bad afterall, i sometimes get lazy with coding html and a convenient switch function in dreamweaver does the trick. so long i still inspect the code now and then … =)

till then…