Hi,I seem to have lost my ability to use the design view in Dreamweaver with the new template changes. This is particularly noticable in my subweb websites. ( I have a wdn folder at the same level of the subweb folders.) Here are two images of the same webpage in Design view of my Dreamweaver CS5. The first is with a WDN folder of the version prior to the changes rolled out on 7/1/2011. The second is a view of what happens when I change the WDN folder to the new design. I checked with Mark Hiatt and Brett Beiber they have no idea. Any Ideas?

I've been having the same trouble with the design view since July 1 and have talked to Trish and Mark trying to figure out any similarities that might cause this. My co-worker does not have this issue on her computer.

Also, since this morning, many of our tables have been disrupted, so our images and text are now misaligned for some reason. What's been changed, does anyone know?

In most (if not all) browsers, if you set a "vertical-align" property in CSS, it will ignore the deprecated "valign" HTML4 attribute. This causes issues for people that still use the technically valid attribute to set vertical alignment.

"Baseline" vertical alignment does not look very attractive when images are used inside tables. Perhaps we need to establish a better default. The default in Firefox is middle (which was overridden).

If you are looking for a quick-fix, you may can add the following to your local CSS to establish a better default vertical alignment. I have added this to the template code repo, so it is currently being evaluated by the other contributors before it is rolled out as an official fix.

The templates use a CSS "reset" stylesheet . . . [that] sets the default "vertical-align" property of all table elements (table, caption, thead, tfoot, tbody, tr, th, td) to "baseline". . ."Baseline" vertical alignment does not look very attractive when images are used inside tables. Perhaps we need to establish a better default. The default in Firefox is middle (which was overridden).

If you are looking for a quick-fix, you may can add the following to your local CSS to establish a better default vertical alignment. I have added this to the template code repo, so it is currently being evaluated by the other contributors before it is rolled out as an official fix.

How about the original question of this thread anyone-----Dreamweaver and Design View?

Eric and Kevin have looked into this issue and have determined that Dreamweaver cannot parse the font declarations and stops parsing the CSS file. We've re-arranged the source so that the font declarations are as late as possible to work around Dreamweaver's poor CSS parsing, and hopefully this will fix the issue.

If you could update your local wdn folder with the latest from the WDN website and report back if the issue has been resolved, that would be great.

mmesarch1: Getting "Design-Time" view to work perfectly would be like trying to get the templates to render for some obscure, not-standard compliant, erroneous browser. Please keep in mind that Dreamweaver (as much as it would like to be) is NOT an internet browser. It does not follow the same "rules" for rendering content in its design view.

That said, the UCOMM staff has worked diligently to make sure what Dreamweaver "displays" is relatively similar to what the browser will render. Admittedly, the differences have been more than apparent in this iteration and the last. For example:

the "N" is in the wrong place

the headings are the wrong font/position

certain elements seem to float in the wrong place

the navigation never renders just right

All of these issues are simply, mostly un-fixable the way Dreamweaver renders its own templates. UCOMM staff has tried to accommodate the most important part of the page, the #maincontent. To that end, styles should (since the last zip update) reflect what they should be (minus a font issue).

More background on the remaining issues:

The entire body of the page has the wrong font:This is again an issue with the new reset.css that is common practice to use. All supported browsers are able to parse the CSS and rendered as expected. Dreamweaver's Design time cannot. I deem this a bug of Dreamweaver.

The breadcrumbs/navigation have no styles:The "Editable regions" of Dreamweaver are delineated with HTML comments. That means they work great for anyone, even if they don't have Dreamweaver to enforce their constrains. However, when Dreamweaver renders those comments in its Design view, it actually creates some kind of "invisible" element in the markup (<mmtinstance:editable>).This means that CSS 2.1 styles that "cross the boundaries" of an editable and non-editable region will not render. Ex:

will not render in Dreamweaver because of the invisible child between #navigation and the first UL child. The navigation and breadcrumb CSS make extensive use of that kind of CSS selector, so they look like crap in Dreamweaver. I deem this another bug of Dreamweaver

UCOMM may continue to look at ways to improve the Design view experience, but until these Dreamweaver bugs are fixed by Adobe, we can only try to come up with buggy work-arounds that don't hurt the actual design. You, of course, are more than welcome to try and come up with your own "Design-time" stylesheets that will work best for you.

Please note: that Dreamweaver (at least in CS4+) has "Live View" that allows you to view your local copy inside Dreamweaver. That may also be a suitable solution.