Much of Dreamweaver's appeal centers around the Design View
interface, which does a pretty good to very good job of rendering a page's CSS and HTML into a fair approximation of what the browser will display via the WebKit framework. Unlike a typical preview, web page authors can continue to edit the page content in this mode and, depending on settings, see placeholder icons for line breaks, positioned elements, code snippets, and much more.
Some users complain that Design View reacts so slowly as to become almost unusable and report having keystrokes take between two and three seconds to reflect on the screen. This can be due to one of several factors:
1) Due to the load of having to draw and redraw the layout and CSS styles as the author types content into Design View, Dreamweaver may become a little laggy. This information comes from David Powers (author of several books on Dreamweaver and one of Adobe's Community Professionals) in a slightly acrimonious Adobe forum thread
. According to Mr. Powers:
Rules that apply to the <html> or <body> tags or that affect more than 10 elements force Dreamweaver to repaint the page completely.
His solution is to make sure your CSS declarations are as tightly targeted as …