"Design" view bug?

I've created a simple menu with CSS. The menu displays differently in "Design" view within DW than it does as an actual rendered HTML page. WTF?
See below the sample I put together that illustrates the difference. The background color is different, the extent of the back color is also different, and even the size of the boxes is slightly different. The DW view is inaccurate, but why?

Hi
Design view is only an approximation and depending upon you code can be a very rough approximation.
PZ

Similar Messages

White box keeps appearing over list items in design view, I want to know why ?

In my footer area, I have 4 vertical lists that act as my sitemap links, but when I hover over them in design view the entire list gets replaced with a white box and then when I move my mouse away the white box disapears and the list shows again. This does not happen in live view but I would like to know why it does that, or if this will happen when the site goes live, or it just a design view bug.
thank you for any help
<ul class="SiteMapLinks">
<li>
<h3>Your Account</h3>
</li>
<li><a title="My Account" href="/my-account/">My Account</a></li>
<li><a title="Track Repair Status" href="/repair-status/">Track Repair Status</a></li>
<li><a title="Protection Plans" href="/protection-plans/">Protection Plans</a></li>
<li><a title="Schedule Appointment Portal" class="track_portal_link" href="replace" target="_blank">View My Appointments</a></li>
<li><a title="Warranties" class="track_portal_link" href="replace" target="_blank">Manage Warranties</a></li>
<li><a title="Remote Login" class="track_outgoing_link" href="replace" target="_blank">Remote Login</a></li>
</ul>
.SiteMap {
margin-top:450px;
padding-top:25px;
margin-left:auto;
margin-right:auto;
width:1050px;
color:#FFF;
height:200px;
background-color: #4695CD;
padding-left: 25px;
padding-right: 25px;
border-top: 1px solid black;
.SiteMapLinks {
float:right;
min-width:70px;
margin-left:28px;
.SiteMap ul {
list-style:none;
padding:0;
.SiteMap a { color:#FFF; }

This is all my CSS
/*** Global Settings *************************************************/
body {
/*Box Model*/
margin: 0;
padding: 0;
font-family:Verdana, Arial, sans-serif;
font-size:76%;
line-height:1.6;
color:#4b4c4d;
a {
color:#db6719;
text-decoration:none;
a:hover {
color:#db6719;
text-decoration:underline;
.justify {
text-align: justify;
color: #000;
.testimonial {
font-family: Georgia, "Times New Roman", Times, serif;
text-align: center;
.LeftColumnHeading {
font-family: BatmanForeverAlternate;
text-transform: capitalize;
color: #FFF;
font-size: 36px;
#Wrapper #LeftColumn p { text-align: justify; }
ul, ol {
margin:0;
padding:0 0 1.6em 2.5em;
/*** Headings *************************************************/
h1, h2, h3, h4, h5, h6 {
margin:0;
padding:0;
font-weight:normal;
text-transform:uppercase;
h1 {
font:36px/1.0em Verdana, Arial, sans-serif;
padding:14px 0 30px 0;
color:#000;
.nofontface h1 { font-weight:bold; }
h2 {
font:18px/1.0em Arial, sans-serif;
padding:0 0 10px 0;
color:#db6719;
h3 {
font:15px/1.0em 'BatmanForeverAlternate',Verdana, Arial, sans-serif;
padding:0 0 8px 0;
color:#fff;
.nofontface h3 { font-weight:bold; }
h4 {
font:16px/1.0em Arial, sans-serif;
padding:0 0 8px 0;
h5 { font:12px/1.0em Verdana, Arial, sans-serif; }
.nofontface h5 { font-weight:bold; }
h6 { font:13px/1.0em Verdana, Arial, sans-serif; }
/*** Commonly Used Styles *************************************************/
/***Wrapper *************************************************/
#Wrapper {
/*Box Model*/
position: relative;
height: 1200px;
width: 1100px;
margin: auto;
/*Layout*/
background-color: #FFF;
border: 1px solid #F0F0F0;
/***Topbanner *************************************************/
#TopBanner {
/*Box Model*/
height: 40px;
width: auto;
margin:auto;
/*Layout*/
background-color: #2783C4;
border-bottom-width: 1px;
border-bottom-style: solid;
border-bottom-color: #226FA8;
#Home {
/*Box Model*/
float: left;
height: 30px;
width: auto;
/*Presentation*/
color: #FFF;
font-size: 16px;
background-color: #2783C4;
margin-left: 5px;
margin-top: 4px;
#PhoneNumber {
/*Box Model*/
float: right;
height: 32px;
padding-top: 3px;
padding-right: 5px;
/*Presentation*/
color: #FFF;
font-size: 15px;
background-color: #2783C4;
width: 230px;
font-weight: bold;
/*** Main Logo *************************************************/
#Logo {
/*Box Model*/
height: 180px;
width: auto;
margin: auto;
/*Layout*/
background-repeat: no-repeat;
background-image:url(../../Header%20Logo6.3%20flat%20.png);
border-right: thin solid #F3F3F3;
/*** Main Menu *************************************************/
#Menu {
height: auto;
width: 1100px;
background-color:#FFF;
padding:0px;
float: left;
border-bottom: 1px solid #dedede;
/*** Testimonial *************************************************/
#Testimonial {
/*Box Model*/
height:auto;
width: 1050px;
margin: auto;
padding-left: 25px;
padding-right: 25px;
/*Layout*/
background-color: #FEFEFE;
font-style: italic;
text-align: justify;
padding-top: 15px;
padding-bottom: 20px;
color: #000;
float: left;
border-bottom: 1px solid #dedede;
/*** BreadCrumb Trail *************************************************/
#BreadCrumb {
/*Box Model*/
Float:left;
height: 28px;
width: 1100px;
/*Layout*/
background-color: #FFF;
color:#000;
ul, li {
list-style-type:none;
padding:0;
margin:0;
#crumbs {
height:1.7em;
border-top: 1px none #dedede;
border-bottom: 1px solid #dedede;
border-left: 1px solid #dedede;
#crumbs li {
float:left;
line-height:1.7em;
color:#000;
padding-left:0.75em;
#crumbs li a {
display:block;
padding:0 25px 0 0;
background-image: url(../_Images/crumbs.jpg);
background-repeat: no-repeat;
background-position: right center;
#crumbs li a:link, #crumbs li a:visited {
color:#000;
text-decoration:none;
a:link, a:visited, #crumbs li a:hover, #crumbs li a:focus { color:#00F; }
/*** Main Content Area *************************************************/
#LeftColumnTitle {
background-color: #4695CD;
height: 40px;
width: 1075px;
float: left;
padding-top: 10px;
font-size: 35px;
color: #FFF;
text-align: right;
padding-right: 25px;
#LeftColumn {
/*Box Model*/
Float:right;
height: 500px;
width: 700px;
/*Layout*/
background-color: #FFF;
padding-top: 20px;
text-align: justify;
border-right: thin solid #F7F7F7;
padding-right: 25px;
#RightColumn {
/*Box Model*/
Float:left;
height: 500px;
width: 250px;
/*Layout*/
background-color: #FFF;
/*** side navigation   *************************************************/
/*** Footer   *************************************************/
#Footer {
/*Box Model*/
height: 700px;
width: 1100px;
/*Layout*/
color: #FFF;
clear: both;
border-top: 1px solid black;
.SiteMap h3 span {
color:#000;
font-family:Verdana, Arial, Helvetica, sans-serif;
font-size:1em;
font-weight:normal;
/*** Footer SiteMap   *************************************************/
.SiteMap {
margin-top:450px;
padding-top:25px;
margin-left:auto;
margin-right:auto;
width:1050px;
color:#FFF;
height:200px;
background-color: #4695CD;
padding-left: 25px;
padding-right: 25px;
border-top: 1px solid black;
.SiteMapLinks {
float:right;
min-width:70px;
margin-left:28px;
.SiteMap ul {
list-style:none;
padding:0;
.SiteMap a { color:#FFF; }
.SiteMap .primary_links a { color:#000; }
.SiteMap a:hover, {
color:#fff;
text-decoration:underline;
/*** Footer contact info   *************************************************/
#ContactInfoFooter {
color: #000;
background-color: #00F;
position: relative;
height: 350px;
width: 300px;
float: left;
clear: right;
/*** Footer company overview   *************************************************/
#CompanyOverview {
background-color: #4695CD;
height: 350px;
width: 299px;
float: left;
/* [disabled]border-right: 1px solid black; */
/*** Footer chatbox   *************************************************/
#Chat {
background-color: #4695CD;
height: 100px;
width: 300px;
float: left;
/*** Footer newsletter   *************************************************/
#Newsletter {
background-color: #4695CD;
position: relative;
height: 100px;
width: 399px;
float: left;
border-left: 1px solid black;
/*** Footer testimonial output   *************************************************/
#TestimonialOutput {
background-color: #4695CD;
position: relative;
height: 350px;
width: 400px;
color: #000;
float: left;
/*** Footer Chatbox   *************************************************/
#ChatBox {
background-color: #4695CD;
float: left;
height: 350px;
width: 400px;
position: relative;
/*** Footer PaymentMethods *************************************************/
#PaymentMethods {
background-color: #4695CD;
float: left;
height: 100px;
width: 400px;
position: relative;
/* [disabled]background-image: url(../_Images/payment-accepted.jpg); */
background-repeat: no-repeat;
/*** Copyright Area *************************************************/
#Copyright {
background-color: #4695CD;
height: 20px;
width: 1050px;
color: #FFF;
clear: both;
padding-right:25px;
padding-left:25px;
border-top: 1px solid black;
padding-top: 10px;
padding-bottom: 5px;
.PrivacyPolicy {
float:left;
.TradeMark {
float:right;
#Copyright .PrivacyPolicy {color: #95896C;font:13px georgia; }
#Copyright .PrivacyPolicy li {
margin:0;
padding:0, 40px;
list-style:none;
float:right;
font:13px georgia;
color:#FFF;
#Copyright .PrivacyPolicy a {
color: #FFF;
border-right:1px solid #FFF;
padding:0 5px;
}

CS3 Design View layout bug

Note: this renders correctly in browsers and DW 8 design
view.
Does anybody else get this effect: css is used to but a solid
background colour on a h1 tag. With the following code

<h1>Introduction</h1>
The editor buts the background in the correct place, but the
actual h1 text starts 2/3 they way down the background.
If you put a blank div <div></div> after the
template comment and before the <h1> the background gets
padded down to fit correctly with the text.
If you detatch from the template, it renders correctly.
Bug I assume.
Steve

Probably not. Show us the whole page, please.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"srbutler" <[email protected]> wrote in
message
news:f2ek5g$51c$[email protected]..
> Note: this renders correctly in browsers and DW 8 design
view.
>
> Does anybody else get this effect: css is used to but a
solid background
> colour on a h1 tag. With the following code
> 
> <h1>Introduction</h1>
>
> The editor buts the background in the correct place, but
the actual h1
> text
> starts 2/3 they way down the background.
> If you put a blank div <div></div> after the
template comment and before
> the
> <h1> the background gets padded down to fit
correctly with the text.
>
> If you detatch from the template, it renders correctly.
>
> Bug I assume.
>
> Steve
>
>
>

BUG: JSP disappears from design view with MyFaces / Tomahawk

Hi,
When I try to create a JSF JSP in design view (as opposed to code view) using MyFaces and Tomahawk 1.1.3, the design view will blank and display "Type, paste or drag and drop content onto this blank....". This usually happens after I've dragged half a dozen JSF outputlabels and inputtext boxes. The code still exists in code view, and will even compile and deploy ok, it's just the design view that stops working. The design view usually blanks while I'm switching between the code tabs at the top of the screen, although I'm fairly sure it blanked as I dropped a textbox onto the form once.
I've restarted JDev, tried to create a second page, clicked refresh etc but I can't get it back. This has happened starting from scratch 3 times now.
I've switched back to the builtin reference implementation JSF (and no Tomahawk), and JDeveloper works fine, so it seems to be a problem using MyFaces. I've added MyFaces and Tomahawk via Manage Libraries.
This Oracle article - http://www.oracle.com/technology/products/jdev/101/howtos/myfaces/index.html
states that the RI version can't be swapped out in JDev Developer Preview version but I understand that's not true now?
I'm using :-
JDeveloper SU4
java 1.5
Windows XP SP1
Thanks for any help.

I found the answer. I went to View, Style Rendering and clicked several of the boxes Display Media was one.

BUG: Extending JDialog error in design view

I extended JDialog to create a custom Dialog, then when I extend the CustomDialog to create a Dialog in Jdeveloper Design mode it actualy creates the popup dialog instead of the design mode for it (ie it actually renders the final popup as a seperate popup, which would be a really cool feature because you can actually use the popup to test it, but it means you can't edit it with the gui designer)
OS - Suse 9.3
Oracle IDE - 10.1.3.3412
Java Platform - 1.5.0_06
Here is some sample code:
package org.cms.custom.swing;
import javax.swing.JDialog;
public class CustomDialog extends JDialog
public CustomDialog()
package org.cms.screen;
import org.cms.custom.swing.CustomDialog;
public class TestDialog extends CustomDialog
public TestDialog()
So you go to design mode for TestDialog and it pops up the dialog.........(you may need to build first).....

The above code does reproduce the error. I reduced it to that code to make sure that it wasn't any of my code doing it and when I made the 2 classes above and go to design mode for the second one it pops up the dialog. You can cut and paste the code as is. The implementation is irrelevant, its Inheritance of a class that extends JDialog that is causing the problem.
You need to compile the classes, close them, then reopen the second one in design view for the popup to happen.
Regards
mark
Message was edited by:
user481304

Auto Inserting tags in Design View

Hi,
I keep running into a problem that is bugging the crap out of
me and I was hoping the Dreamweaver community could help me solve
it.
Whenever I am in Design View, and I add, say a table, then
type some text inside any of the cells, there is a opening and
closing p tag that automatically is added around the text.
p tags are no good for me because stylesheets in my CMS
controls the p tags and in order to avoid this from happening, I
would have to apply styling to every page, which obviously is
horribly inefficient. I figured Dreamweaver being the powerful
beast of a website editor it is, would have some option that allows
me to either turn this off entirely, or modify what gets added.
Could someone help me out?
Thanks!

On Fri, 1 Aug 2008 20:00:44 +0000 (UTC), "bothead1"
<[email protected]> wrote:
>Hi,
>
> I keep running into a problem that is bugging the crap
out of me and I was
>hoping the Dreamweaver community could help me solve it.
>
> Whenever I am in Design View, and I add, say a table,
then type some text
>inside any of the cells, there is a opening and closing p
tag that
>automatically is added around the text.
>
> p tags are no good for me because stylesheets in my CMS
controls the p tags
>and in order to avoid this from happening, I would have
to apply styling to
>every page, which obviously is horribly inefficient. I
figured Dreamweaver
>being the powerful beast of a website editor it is, would
have some option that
>allows me to either turn this off entirely, or modify
what gets added.
>
> Could someone help me out?
>
> Thanks!
Don't touch the return key them
I just tested it on Dw CS3 - brand new page - created new
table, and
entered text.
No <p> tags -
but if you hit return key - it put in a new paragraph - as
one might
expect
~Malcolm~*...
~*

Flashplayer10 afcs.swc, components not shown in Design view

Hi,
When I use the FlashPlayer10 swc nothing is shown in the Design View.
Is that bug ? isn't it just not working here ?

Hi, could you please try the followijg code and tell me if you can see the visual components in design view.
Make sure you try it with afcs.swc for Player 10 and Compiler set to 10.0.0
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" xmlns:rtc="AfcsNameSpace">
     <mx:RemoteObject showBusyCursor="true"
          id = "afcsService"
          destination = "afcsChat">
          <mx:method name="afcsAuth" result="afcsAuthResult(event)"/>
     </mx:RemoteObject>
     <mx:Script>
          <![CDATA[
            import mx.rpc.events.ResultEvent;
            private function getToken():void{
                 afcsService.afcsAuth();
            private function afcsAuthResult(e:ResultEvent):void{
                 auth.authenticationKey = String(e.result);
                  session.login();
          ]]>
     </mx:Script>
     <mx:Button x="10" y="10" label="Login" click="getToken()"/>
     <rtc:AdobeHSAuthenticator id="auth" />
     <rtc:ConnectSessionContainer autoLogin="false" id="session" width="100%" height="100%"
          authenticator="{auth}"
          roomURL="http://connectnow.acrobat.com/whomzour/videochat">
          <rtc:SimpleChat width="363" height="151" x="10" y="291"/>
          <rtc:WebCamera width="361.5" height="235" y="48" x="10"/>
          <rtc:AudioPublisher />
          <mx:List dataProvider="{session.userManager.userCollection}"
                  labelField="displayName" x="379.5" y="48" height="394" width="155"/>
     </rtc:ConnectSessionContainer>
</mx:Application>

Dreamweaver 8 Design View render issue

I was wondering if anyone else has noticed a highly
irritating issue with DW8 that is apparently not an issue in the
Design View of DW MX 2004.
In DW 8 for some reason I'm getting an extra 150 pixels of
white space to the right of my #content container. It only appears
to happen when the content within the #content container does NOT
exceed the length of the content in my menu container (#priNav2).
In other words, if the content is longer then the menu, it renders
fine.
See here:
Dreamweaver
8
But, in DW mx2004 the exact same file shows up how it should.
Dreamweaver
MX 2004
Does anyone have any suggestions on how to resolve this issue
or have a clue as to why this is happening? It's really one of the
only bugs left preventing me from upgrading to DW 8 anymore.
Thanks,
- Paul

After some tinkering around and a call to Tech. Support I
eventually resolved this issue by pointing out a bug to Adobe.
Apparently the problem is the View / Visual Aids / Invisible
Elements option. If this is turned on, and you have a website set
up similiarly to
this one, you will
experience this sporatic, extranenous white space that shifts your
content around. It is not an issue in DW MX 2004, only DW 8.
The solution is to just simply turn OFF the "Invisible
Elements" option. Then the page will render the way it should.
A bug report has been submitted.

Problem with Design View in DW5

I've recently inherited responsibility for my group's website (despite the fact that I'm kind of a noob at all this) and am dealing with an interesting challenge that I hope someone can help me with.
It seems that our pages are based on a number of templates that for some reason were not saved along with the rest of the site. Short term this is not a huge issue, as the pages have the source code from the templates embedded in them, but this code is not editable and I can't figure out a way to override the fact that I'm "locked out" from making any changes (at least from within Dreamweaver). Up to now I've just been editing the pages individually in Komodo, which is tedious but not horrible, given that our site isn't that big, but it's clearly no way to do business in the long term.
So I'm trying to re-engineer some templates that I can work with. What I did was use Komodo to strip away all of the template-related language from one of the site pages, and re-imported the code back into Dreamweaver, in the hope that I can then save that as a new template. I'm close, but not quite there. My problem is that DW's Design View isn't rendering the page properly, even though it displays fine in Live View and in browsers. Maybe this isn't a huge deal, but it's really bugging me because: 1) I do rely on Design View, since I'm not an experienced programmer; and 2) I'm kind of anal retentive.
To see what I'm talking about, here is the page I used as the foundation for creating a new template:
http://iodp.ldeo.columbia.edu/TOOLS_LABS/TRIPLE/aps.html
... and here is my new "template" (although I haven't saved it yet as a DW template):
http://iodp.ldeo.columbia.edu/TOOLS_LABS/TRIPLE/test3.html
The second page displays correctly in Live View, Safari and Firefox, but not in DW's Design View, where it looks like this, at least on my computer:
As you can see, there's an odd "break" between the banner image and the menus on the left, and the body of the page, which should appear to the right of the menus on the left, is instead underneath them. I'm at a loss as to why the same code displays properly for the first page, but not the second.
I guess my questions are as follows:
1) Does anyone else get the same messed up display in DW's design view if they import the second page into DW?
2) And if so, can you pinpoint where the problem is?
I hope I've explained this clearly and would really be grateful for help. Thanks!

Validate your code and fix errors. #1 problem is the lack of a valid Document Type Declaration (DTD) on line 1 of HTML code.
Code Validation Tools
CSS - http://jigsaw.w3.org/css-validator/
HTML - http://validator.w3.org/
To add a DTD in DW:
Go to Modify > Page Properties > Title/Encoding.
Select document type from drop list. I recommend HTML 4.0 Transitional.
Hit Apply & OK.
Repeat Steps 1 - 3 on remaining site pages.
I'm not a huge fan of DW Templates (.dwt). I don't know how big your site is but it might be simpler to disconnect from Templates, giving you freedom to edit anything you wish. Then use Server-Side Includes (SSIs) for common site wide elements such as menus, headers & footers.
The great thing about SSIs is that you only need to edit one file, save it and upload to server. Site pages are automatically updated by the server. With Templates, you have to upload every child page each time you change your template. Even on small sites, this is tedious.
Server-Side Includes
http://www.smartwebby.com/web_site_design/server_side_includes.asp
More on Server-Side Includes
http://forums.adobe.com/message/2112460#2112460
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/

Flash Builder Design Mode Bug Workaround (!!!)

I've been fighting this annoyance since FB4 came out, and while I still don't think that custom/embedded fonts in design view are fixed by this, I've been able to reproduce this "fix" (workaround) to get design view to show fonts/theme correctly under some very specific circumstances on two separate PCs.
If anyone from Adobe sees this I'd like to know whether this sounds familiar or is possibly logged as a bug already somewhere in JIRA.. if not I could probably do that as long as it won't be a wasted effort.
The problem:
You're using a Halo theme but certain CSS settings (specifically and possibly limited to FONTS) don't work properly in design view even though they work fine in Flash. Essentially this makes design view practically useless since choice of font family, size, and weight can effect component sizing if you aren't hard-coding component sizes (ugh)... ruining your efforts to use design view for UI design if your UI has any level of complexity (or uses absolute positioning at all).
The specific circumstances seem to be:
You're using the Halo theme (you have no special 'skinning' requirements and want Halo defaults w/only CSS customizations)
You've upgraded a Flex 3 project to Flex 4 SDK (not sure if this is needed to reproduce the issue)
Using a regular non-embedded font (embedded fonts still do crap out, but even this 'workaround' doesn't fix that problem)
You're using swc library files such as the Swiz lib, Mate, Flexlib, etc. (I think it's ANY swc, not specific to any one)
This may also only apply when using an "mx only" project (no Spark), since we're using Halo here
The two part fix (as far as I can tell you need BOTH before design view works correctly):
In .actionScriptProperties, add the following bolded line after the compiler tag like so:
</compiler>
<theme themeIsDefault="false" themeIsSDK="true" themeLocation="${SDK_THEMES_DIR}/frameworks/themes/Halo"/>
<applications>
(I think this may only apply to 'upgraded' projects, as the line does seem to be present in newly created FB4 Halo projects. My guess is that an "upgraded" project should have such a line added, but doesn't get it due to an oversight/bug.)
The somewhat painful, and definitely odd part. Remove all your SWC library files from /libs. Grab the source code for the libraries and drop them into your project's /src folder as if you'd written them yourself. (This may require some research and knowledge on special requirements to build the libs, such as with Swiz's compiler metadata compiler settings which you need to put into your project's settings.) After you get things set up right and the project compiles again, doing a refresh of design view should finally give you proper looking Halo controls and fonts so they look identical to the Flash runtime view.
Why this works, I've no idea. I suspect it has something to do with that stupid and annoying (and supposedly 'harmless') design mode warning message you get when you include a library like Swiz or Mate in your project. (Design mode could not load xxxxxxxxxxxxx.swc. It may be incompatible with this SDK, or invalid. (DesignAssetLoader.CompleteTimeout)) - this warning doesn't break your application, people seem to think it's just a harmless warning..but is it breaking design view?
If anyone has any idea what's going on here, why this 'fixes' the problem (a better work around), or has any other insight I'd love to hear it. The combo of needing to do two things (in my specific case) to fix the problem really made this a ROYAL PAIN, I still can't believe I found it.

Hi Fernando, sorry for the delayed response. CSS Design Mode is not available for Flex 4 projects, but it is still available in Flex 3 projects. The reason for this is that designing components in Flex 4 is often a lot different, since it relies highly on the new spark skinning architecture. There is, however, an Appearance panel available in design view which supplies a set of the main inheriting styles. Setting these styles in the Appearance panel will result in assigning values to a global style selector.
I hope this helps,
Rob

Unable to view page content in Design View

I cannot see the content of a page made from a template in normal Design view.
I am able to see the content in Live View mode, but cannot make changes in that view. I can only make changes in code view.
My client would like to make changes to content text in Design view only.
Why am I unable to see/edit in Design view?
Two screencaps and the page code are here:
http://compassdm.com/GM/
I am using CS4 DW on Macbook Pro, Leopard.
The template is based on the standard included thrColAbsHdr layout template provided with DW.
Thank you for help.
BW

DavidHonaker wrote:
There are two questions for the Spry Menu 2 version.
1) Do I have to make all menu title and link changes in code? With the regular Spry menu that comes with DW CS5 you can make the changes, and add links to menu items, in the "Design > Properties" window. I would sure like to be able to do that, rather than go to the strictly "code" view and work in there.
2) With the Spry 2 menu at the top ( see www.Aloe-Vera.org/test.htm ) I am unable to go into "Design" view for the page to make changes in the content of the page itself.
Are there any fixes so that I can view and edit the rest of the page in DW CS5 "Design" view?
Thanks, David
1. It is true you cannot use the Properties window. You can use the code view or the Widget Browser to make edits. The Widget Browser has a GUI if you feel more comfortable with that.
2. You should be able to make some changes in Design View, but unfortunately the GUI and clean layout in Design View is gone. Best suggestion I can give you here is to file a bug report/feature request: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform . I have before with this because I agree it helps newer users and compared to commercial alternatives like those from Project Seven it falls short everytime.

DW CS5 "Design view" question

Let me start by saying I'm very new to using DW and I'm getting all my GoLive sites moved over slowly.
For some odd reason in Design View, DW CS5 (Win) displays all the text on the page in bold type - making it impossible to tell what is or is not bolded in the actual view. It's very inefficient to have to check everything in the Live View to see what's bold and what isn't that needs to be.
I've looked though all the settings and options menus I could find, but can't locate where I can fix this glitch. Help would be MOST appreciated!
THANKS.

GoliveFan wrote:
My problem isn't with live sites, it's when I'm working on my computer with any site pages that all the text in the Design View is in bold. When I switch views to "Live View" it displays correctly.
Can you post a link to the code then if it has been something since you started? It's possible you may have discovered some odd bug with the code on your page but unless you post a link we are just shooting in the dark and can only guess.

Why can't I drag images from Finder to Design View Dreamweaver CC?

Hey Guys,
I'm using OS X Mavericks (10.9) and Adobe DW CC
For some reason in both CC and CS6 I can no-longer drag files from Finder (Mac OS X's Explorer) into the design view ( for eg: adding images to a table cell ), the browse button doesn't work properly either... The "browse for file" button only works if there is an image already there and then it will update the image, otherwise if there's no image in the table cell it will bring up the browse dialogue box but does nothing if I select a file and press "open".
Is there a setting that was introduced in CS 6 that affects this behavior?

Hi All,
This bug has been fixed in the latest version of Dreamweaver CC 2014, which is now available for download.
Download it from https://creative.adobe.com/ or directly through the Creative Cloud desktop app.
We’re excited to hear back from you. Please share your feedback.

Inserting DIVs in HTML view screws Design view but preview is fine

RH8 HTML
Hi all,
Ive been working on a fix for a client, forcing a footer banner to the bottom of the screen, regardless of content in the page. Its nearly working fine, just a bit more tweaking, but one problem I am having.
I am editing and adding <div> in HTML view, so that the positioning works.
However, when I view the page in Design view, its all messed up, the content is really narrow and stretches down the page for a long time. However, when I preview, and generate the page it looks fine.
Its an issue, because the client will be given the RH source files at the end of the project, and with the front end editor looking like this its not going to be weasy for the to edit it, let alone me finish with all the content.
Has anyone come across this before? Is the Design viewer not the best at displaying div content ?
The HTML where the <div> is set off before content is entered:
<body>
<div id="wrap">
    <div id="main">
        <div id="spacing">
***********all content in here************
          </div>
    </div>
</div>
</body>
The CSS that the <div> is calling
#wrap {
    min-height: 100%;
    border-left: 1px solid #9ea6ad;
#main {
    overflow: auto;
    padding-bottom: 54px;
/* must be same height as the footer */
#spacing {
    padding: 10px;
#footer {
    position: relative;
    margin-top: -54px;
    height: 54px;
    background: url(footer.gif) repeat-X;
    clear: both;
    border-left: 1px solid #9ea6ad;
/* negative value of footer height */
#footer p {
    padding-top: 15px;
    padding-right: 10px;
    color: #ffffff;
    font-family: Arial, sans-serif;
    font-size: 10pt;
    text-align: right;
/*Opera Fix*/body:before {
    content: ;
    height: 100%;
    float: left;
    width: 0;
    margin-top: -32767px;

Hi Nick
What you are doing is working outside the boundaries of what RoboHelp natively does. If working with DIVs was part of that you wouldn't be forced to create them in the HTML view. As a result, I'm not surprised that the Design view isn't totally understanding how to deal with it.
No workaround I can think of here. Sorry about that. Maybe someone else has something to offer. What I'm posting to ask is that you please report this to Adobe as a bug. Who knows, maybe they have some magickal scripting or something they can do to accommodate it. At minimum, they need to be aware of the issue so they can factor it into a future release. Use the Feature Request link in my sig.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7 or 8 within the day - $24.95!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

DW CS3 problem with PNG-8 images in Design View?

DW CS3 (build 3481) on XP seems to have problems with PNG-8 images, specifically trying to display them in design view.
I had a very simple image that was able to be exported by Fireworks CS4 as PNG-8 using 4 colors (no transparency) for a tiny file size under 250 bytes.
DW could not display it at all, or even recognize it, reporting it was 0 x 0 in size. I published the page anyway, and it looked fine in the browser.
I upped the number of colors to 32, and DW could then display it in design view in the page I was working on.
I'm still having problems with other PNG-8 images. The attached file "temp.jpg" is a screenshot showing part of the design view in DW.
The smaller image on the left of the banner is "58_certificate_of_discharge.png" (attached), and the larger image below is used as the background of the DIV containing the form,"compassbk.png" (also attached).
These images all look fine in the browser, but terrible in DW.
I'm stumped as to why.
Thanks in advance.

According to a different discussion, the images that are stuck as "Queued" are showing a bug in the virus scanning on the forums.
Now trying the recommended 'camera icon' method...
Looks like it worked.
Now compare what it looks like in DW CS3 in the design view:
It's a 16 color PNG-8 made in Fireworks CS4 with no transparency, size is 113 x 58, ending up at 1.71K.
If this is a repeatable problem in CS3, is there any hope of it being resolved, or am I stuck with upgrading to CS4 as my only option (assuming it's fixed in CS4)?
Thanks.

"Design" view bug?

Similar Messages

Maybe you are looking for