Dreamweaver CS5 Bugs

by James Cook on October 4, 2010

Update: I'm bumping this post and updating it with an annoying (but not damaging) bug in the Mac Version of Dreamweaver CS5.

Sometimes, double-clicking on a style name in the CSS Styles Palette will cause the list of style rules to disappear (rather than opening the CSS Rule Definition dialog).

Actually the list seems to have just scrolled left out of the visible part of the palette. If you encounter the problem:

1. Don't panic.

2. Double click again in exactly the same location

OR if you've already moved your cursor

2 (alt). Move the scroll bar at the bottom of the Styles palette back to the left to bring the rule names back into the palette window and try again.

IMPORTANT: You can always edit a style rule by left+clicking on the rule name in the CSS Styles palette and selecting Edit from the pop-up menu.

Remember, as far as I have determined, this is a Mac-only issue and seems to happen erratically. PC users shouldn't be affected.

Let me know if you discover other issues.

Update: Adding another bugs, this one involving the Spry Assets folder.

1. It appears that Mac users with hard drives with a name that includes a space may be subject to an error (Spry Assets folder is not in the local site folder - even though it is) when they try to set up their sites. The "solution" appears to be to rename their hard drive which of course can mess up a lot of other things (including other site definitions). Here's a discussion on the Adobe forum: http://forums.adobe.com/message/3053791#3053791


I've come across a couple of bugs in Dreamweaver CS5 so I thought I'd share them with other Dreamweaver users and invite you to share any other bugs you come across. Here's what I've found:

1. Double+clicking a style in the CSS Styles palette (sometimes) causes the style names to disappear. Double clicking again in the same spot opens the style editor (Mac). I haven't yet been able to duplicate issue #1 on a PC (and I'm afraid, if it's Mac-only, I'll have to wait a very long time for Adobe to deal with it).

2. If you create a page from a template that has an editable region behind a non-editable div with the CSS overflow property set to auto or hidden, there is no way to select the text of the editable region. Pages from the same template work fine in CS4 and (here's the kicker) in CS5 the page begins working correctly if you detach it from the template, select the text and then undo to reapply the template??? (Mac and PC)

UPDATE 8/9/2010: Thanks to Frances de Wall for the work-around for this issue (see discussion in the comments below). You need to attach a Design Time Style Sheet to the template with this CSS rule:

* { overflow: visible !important; }
You can find more information on this issue on the Adobe forum.

Let me know if you discover other issues.

arcantos1618 February 15, 2012 at 11:57 am

Hello, I know this page is a little old but i added an editable region to my template on my site. everything works fine but the region does not have a set width. When you go to enter text on an actual page the text does not wrap back to the beginning of the box but continues till it is off the page. When i view it in a browser it has created a horizontal scroll bar with in the div region. (I have set areas using Div Id’s). any tips on getting rid of the scroll bar and getting my text to wrap back to the beginning?

dwcourse March 3, 2012 at 10:56 pm

The text should wrap to the width of the containing div. I’d need a link to your page to be able to see what the problem is.

Michael January 11, 2011 at 9:52 pm

Hi, We have this problem with the website. It worked fine with the editable region under cs4, but with cs5, the editable region is no longer editable in the Design pane. I’ve tried moving the begin/end editable region tags outside of my overflow hidden objects manually, but it messes up the design for some reason.
I tried overriding overflow, but it also messes up the design. I found one position for the Editable tags that actually allows me to edit in the design pane, but the cursor is still the “NO EDITING” stop sign, so I can only use the keyboard to get around in the design view. So it’s roughly the same as editing the code directly. UGH.

jcook January 12, 2011 at 6:50 am

Did you try creating a Design Time style sheet with this style:

* {
overflow: visible !important;
}

It is a new problem introduced in CS5 but this solution worked for me and Design Time style sheets only apply when you’re editing, not online.

Latoya Bridges December 22, 2010 at 12:45 am

Turns out your solution worked after all. After checking out the forum page you linked to I realized I should just overwrite the overflow property universally in the Design Time Style Sheet rather than doing it on a case by case basis. * { overflow: visible !important; } That did it. I’ve updated the post with the information. Thanks!

Wordpress Template Designer November 13, 2010 at 12:09 pm

It appears that the “design time” feature in CS5 does not work as well as as it had in cs3 and earlier version of dreamweaver. For example if you are using design time stylesheets to work on a file that has no doctype declaration “which by the way is the primary reason why we use “Design Time” design time it does not render margin-left:auto; margin-right:auto which can be extremely annoying. Another bug is that the wordpress code hinting does not work even after you specify the wordpress code hinting option. The list goes on and on and on. To tell you the truth on my computer most of the New features that dreamweaver cs5 offer do not work at all. By the way I am running an I7 with 9GB of triple channel ddr3 ram, and a 1ghz GPU with 1GB of ddr3 ram.

Frances de Waal August 9, 2010 at 8:52 am

That’s good to hear. You can read more about the issue at http://forums.adobe.com/message/3025919#3025919

jcook August 9, 2010 at 10:18 am

Turns out your solution worked after all. After checking out the forum page you linked to I realized I should just overwrite the overflow property universally in the Design Time Style Sheet rather than doing it on a case by case basis.

* {
overflow: visible !important;
}

That did it. I’ve updated the post with the information.

Thanks!

Frances de Waal August 7, 2010 at 2:49 pm

If you have an instance of a template and an editable region in an element with overflow: hidden (or a parent element that has that), the content is not editable but blocked. Solution is to overrule the overflow with a designtime stylesheet with overflow: visible !important; Weird, don’t you think? Adobe has confirmed it is on the ‘buglist’.

Besides that I have had some other very strange things happening, like that, no matter what I tried, I couldn’t add the link I had filled in in the Propertie Inspector, to my selection. Or after working in the source, no way I could refresh the Propertie Inspector. Or I couldn’t change some selected paragraphs into listitems with the button in the Propertie Inspector. But later I couldn’t reproduce it. And next it happens again. Didn’t have time though to check it out any further. I started working with Dw3, work intensively with it and never felt so uncomfortably with a new version.

jcook August 7, 2010 at 3:44 pm

Frances, I appreciate the suggestion but it didn’t work. I’m thinking that, with all the emphasis on other things, Design View might have been overlooked.

Frances de Waal August 9, 2010 at 1:30 am

Sorry, I didn’t mean this as solution for your problem, I just contributed another bug. So my DTSS solution indeed won’t work for your problem.

jcook August 9, 2010 at 7:39 am

Frances, it turns out you bug report was a better explanation of what I was experiencing. I hadn’t connected it to the overflow:hidden property. Thanks.

Comments on this entry are closed.

{ 1 trackback }

Previous post:

Next post:

Home | Make Contact