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

Similar Messages

Dreamweaver CC crashes when switching from code view to design view

I am experiencing a recent problem with a file I am currently working. When I switch from code view to design view Dreamweaver crashes and requests a shut down. Other files seem to work without a problem. This particular files has 3 cascading EdgeAnimation CC files that are selected by media queries. I can test the page online without a problem but not in design or live view.

Since your new page didn't crash, this leads me to believe that you have some critical errors and/or conflicts in your other page(s).
Try running your code through the W3C validation tools.
CSS - http://jigsaw.w3.org/css-validator/
HTML - http://validator.w3.org/
Also debug JavaScript.
JavaScript - http://www.jslint.com/
Nancy O.

Access 2010 on 64 Bit Windows 7 Access "Not Responding" when changing from forms view to design view and back

I am running
Windows 7 64 bit
Access 2010 32 bit
Developing an application with a split FE BE with both files local but continue to have the message "Not Responding" when switching from forms view to design view and back as well as if I try to connect to a subform or object on the sub form.

I have seen this behavior when the form's RecordSource is a complex query such as a crosstab or a query with several nested queries. To test if this is your case, remove the RecordSource and see if the form starts acting normal again.
Then again, if the form has several subforms they might be slowing up the loading time.
Bill Mosca
www.thatlldoit.com
http://tech.groups.yahoo.com/group/MS_Access_Professionals

Live view vs design view

there is one item on my index.html (home) page that floats off to the right when in live view, but when in design view and when viewing live online through IE7 and firefox its fine. the url is www.lowcostloanmodification.com. if anyone can look at it and help me figure it out. my fear is it is showing up live on some other browser that way. When i did a compatability check it seems fine in all browsers.
Message was edited by: greg134

My apologies, I thought I was moving too fast. The item that is moving off to the right is the opt in box reprsented by this code. My friend helped me put this together and he created a shadow box using this code which even me as an amaetuer can tell is not correct. i asssume that is why its moving off to the right outside of the div id = wrap
<div id="sidebar" >
          <div class="opt-in">
              <div id="shadow-container">
                        <div class="shadow1">
                            <div class="shadow2">
                                <div class="shadow3">
                                    <div class="container">
                                        <form id="joinform" method="post" action="https://www.mcssl.com/app/join.asp?">
                                        <h2>Receive Our Free Report:</h2>
                                        <p><strong>"5 Most Recent Loan Mod Developments as of 12/20/09!"</strong></p>
                                        <p>First Name:<br />
                                        <input type="text" name="name1" id="name1" size="14" /><br />
                                        Email Address:<br />
                                        <input type="text" name="email1" id="email1" size="14" /><br />
                                        <input class="button" type="submit" name="submit" value="Get Free Report" />
                                        <input type="hidden" name="Home" value="www.lowcostloanmodification.com" />
                                        <input type="hidden" name="DefaultMailingAR" value="478392" />
                                        <input type="hidden" name="MailingThankyouURL" value="www.lowcostloanmodification.com/index2.html" />
                                        <input type="hidden" name="MerchantID" value="163311" /></p>
                                        </form>
                            </div>
                                </div>
                            </div>
                        </div>
                    </div>
        </div>

Rearanging of my codes when moving from code view to design view

I was wondering if there is a setting in Dreamweaver CC that can maintain the way I wrote my codes?
This is what happening:
I work in code view and write my codes. then I go check it out in design view, then I come back to my codes and Dreamweaver justify my codes... it's really annoying. is there a way to preserve the design (the way I wrote my codes and it will stay as is no matter what)
Side note: I am not talking about split view where it is expected that the code would move around with fluidity. I am talking about full code view. thanks

No I don't mean that... but I think I figured it out.
Here is what I think: Working in design fluid grid layout causes additional codes to be added to my existing codes. I have learned to start keeping a close eye on this because the names of my classes are starting to grow like crazy. I had tried to design something in fluid grid when I first got Dreamweaver (well because, that was one of a major selling point for me) I soon realized that having little exprience in css to start with tripled how complicated it became to apply proper styling throughout a webpage so I went back to the basics and learned how to work with css first. I am getting pretty good at it now and felt it was time to give Fuid grid another shot. I had forgotten about how tricky it is to keep things tight in that environment. So all it was; I am almost 99.9% sure of it was because when I went and changed some setting in the gui I didn't noticed that it tagged another name to my already name class. So in a sense I am getting multiple classes tags for one item. After a while the extra code inserted by Dreamweaver messes up all the code layout (that I have beed trying to keep tidy as much as I can) lol. Gosh! I am really starting to like Dreamweaver, but man O' man... I think I am really starting to hate using the graphical environment and starting to really understand what the old boys keeps on saying that it is best to hard code than trying to adjust things with the graphical environment.

Pages look fine in Design mode but Preview and Publish Distorted Footers

I'm experiencing some unusual issues with Muse. Footers on some of my pages are either not displaying content or distorting them..for example:
http://lawtechpartners.com/consulting.html
In muse Design mode it looks ok - screenshot here:
https://dl.dropboxusercontent.com/u/11434055/muse-screenshot.PNG
But live and in preview mode the issue shows.
I went so far as to delete ALL the files on the server and upload the entire site and all files from scratch to make sure nothing was colliding.
Can anyone help?
Thanks in advance.

Yes - I'm sorry I should have come back in and closed the question. It was all being caused by a very simple and short Google+ code that was to display the Google+ logo. As soon as I removed it, the footer rendered correctly. Here is the offending code:

<div class="g-plusone" data-size="medium"></div>

<script type="text/javascript">
(function() {
    var po = document.createElement('script'); po.type = 'text/javascript'; po.async = true;
    po.src = 'https://apis.google.com/js/plusone.js';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(po, s);
</script>

CQ inserting divs into HTML output?

Hey y'all,
I'm working on a project using CQ5.5 and am noticing a bizarre result in the HTML that I am getting from my templates. I'm noticing divs inserted that appear nowhere in my jsp files that I can only assume are being put there by CQ (because the naming convention "cq-gen#" appears). Example below (textandheading is the name of a custom component I created):
<div id="cq-gen7" class="textandheading text parbase textheading cq-element-textheading">
This wouldn't be a problem except that some of these divs are overriding the styles from the CSS I'm using and causing my text/images etc to display incorrectly. Has anyone experienced anything like this before? It's inserting a whole bunch of divs like the one I pasted in above all over the place. I would like to find a way of removing these divs from my HTML output.
Thanks in advance for your help!

Please try the suggestions mentioned in http://forums.adobe.com/message/4294983
Jörg

Css doesn't show on live view, only design view

I have dreamweaver cc and it should work. It worked yesterday..
My head:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<script type="text/javascript">
<title>Light Up Your World</title>
<script>var __adobewebfontsappname__="dreamweaver"</script><script src="http://use.edgefonts.net/source-sans-pro:n6:default.js" type="text/javascript"></script>
<link href="css.css" rel="stylesheet" type="text/css" />
</head>
... I don't understand why it isn't working anymore. It's in the same map as the Html!

Validate code and fix reported errors. A missing colon, semi-colon or curly bracket might explain the problem.
CSS - http://jigsaw.w3.org/css-validator/
Also validate your HTML code and fix any reported errors.
HTML - http://validator.w3.org/
Nancy O.

GIF won't play in design mode, but previews fine... any ideas?

My animated gif loops in browser preview, but only plays on the stage when i move it around. If I leave it selected without moving, it sits there frozen. Any ideas why my gif won't play properly in design mode? Thanks!

Thank you for confirmation that that is how things should work. I'm new to
the program and following some Lynda tutorials to get up to speed. My most
recent lesson included the gif in exercise files, and everything seems to
function both in Photoshop and the browser. Even in edge design mode, if I
press on the gif and move it around, it plays and loops fine. But as soon
as I stop moving the gif, it returns to first frame and stays stuck there.
Whether selected or not, it just sits there frozen. If I switch
applications and come back to edge, I catch a glimpse of other frames, as
if the gif was playing in the background. But then it stops again, kind of
like a watched pot The behavior seemed glitchy to me, but I thought I
might be missing a setting somewhere. I'll try with other gifs, I guess..
Thanks again!

In PSE9, outputting slideshow to .wmv skews inserted text, but preview is fine.

In Photoshop Elements 9, I created a slideshow, which included text on the slides. The preview looks
exactly how I want it, but when I output to a .wmv file, the text becomes over-sized and spills off the slide
(so only about two-thirds of it is visible). How can I get the outputted .wmv file to look exactly like the preview?
Regards,
Chris

I did try re-doing the slideshow from scratch, and changing all the image sizes to match the output video (1024 x 768). I still got the same problem - until I realized that re-sizing the text window over the slides causes this to happen. I tried experimenting with the text on 2 identical slides, and each time when I re-sized the text box, the text skewed. I can still move the text box around without incident. Any further thoughts on why this happens?
Regards,
Chris

Design view issue - CSS and html

Hi
I was wondering if anyone can help me with this. Someone has
created a page for me using html and CSS as requested. The problem
is that whenever I try to open the index.html file in design view
or code and design view, Dreamweaver crashes and I have to restart.
I am attaching the html and CSS below. Just as an aside, I have
asked them to create the code using CSS rather than tables and have
ended up with div hell.
Cheers
Julie
@charset "utf-8";
* {padding:0; margin:0;}
body {padding:10px 0 10px 0; background-color:#fff; margin:0
auto; width: 976px; font-family:Arial, Helvetica, sans-serif;
font-size:11px; color:#333;}
#wrap {margin:0 auto; padding:0; position:relative; width:
976px;}
a:link { color:#999; text-decoration: underline; }
a:visited { color:#999; text-decoration: underline; }
a:hover{ color:#666; text-decoration: none; }
img { border:none; padding:0; margin:0;}
h1 {font-size: 36px;}
h2 {font-size: 24px;}
h3 {font-size: 18px;}
h4 {font-size: 16px;}
h5 {font-size: 14px;}
h6 {font-size: 11px;}
input { position:relative; font-weight: normal;cursor:
pointer;vertical-align: middle;padding: 0 3px;font-size:
13px;font-family: Verdana, Helvetica, Arial, sans-serif;
border:#a09f6f 1px solid;}
select {font-family: Verdana, Helvetica, Arial,
sans-serif;font-weight: normal;cursor: pointer;vertical-align:
middle;border: 1px solid #999;padding: 1px;background-color:
#FAFAFA;}
option {padding-right: 2px;}
textarea {font-family: "Lucida Grande", Verdana, Helvetica,
Arial, sans-serif; width: 60%;padding: 2px;font-size:
1em;line-height: 1.4em; border:#a09f6f 1px solid; width:390px;
height:170px;}
/* Header Part Start */
#header {margin:0; padding:0; position:relative;
background:url(../images/index_01.jpg); width:976px; height:97px; }
#header .headprt {margin:0; padding:0; position:relative }
#header .headprt .headprtr { float:right; width: 500px;
margin:0; padding:0; position:relative }
#header .headprt .headprtr .padhr { color:#fff; margin:0;
padding:16px 44px 0 0; position:relative; text-align:right;}
#header .headprt .headprtl {margin:0 500px 0 0; padding:0;
position:relative;}
#header .headprt .headprtl .padhl{ color:#fff; margin:0;
padding:40px 0 0 44px; position:relative }
.hhllb { font-size:16px;}
.hhlld { font-size:16px; font-weight:bold}
.hhllc { font-size: 20px; font-weight:bold}
.hhlls { font-size:14px}
.kulay { color:#e55b68}
/* Header Part End */
/* Main Part Start */
#maincontent {margin:0; padding:0; clear:both;
position:relative; display:block; background-color:#fff }
#maincontent .boxmainbgl {margin:0; padding:0;
position:relative; background: url(../images/index_10.jpg) repeat-y
top left; }
#maincontent .boxmainbgl .boxmainbgr {margin:0; padding:0;
position:relative; background: url(../images/index_11.jpg) repeat-y
top right; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
{margin:0; padding:0; position:relative;
background:url(../images/index_02.jpg) no-repeat top left; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr {margin:0; padding:0; position:relative;
background:url(../images/index_05.jpg) no-repeat top right; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr .boxmainbgbotl {margin:0; padding:0;
position:relative; background:url(../images/index_15.jpg) no-repeat
bottom left; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr .boxmainbgbotl .boxmainbgbotr {margin:0; padding:0;
position:relative; background:url(../images/index_16.jpg) no-repeat
bottom right; }
#maincontent .boxmainbgl .boxmainbgr .boxmainbgtopl
.boxmainbgtopr .boxmainbgbotl .boxmainbgbotr .boxpadzki {margin:0;
padding:8px 48px 0 49px; position:relative; height: 1340px;}
.mainconup {margin:0; padding:0; position:relative;
clear:both; display:block; overflow:hidden; height:485px }
.mainconup .mmtoprt { float: right; width:615px; margin:0;
padding:0; position:relative }
.mainconup .mmtoprt .mmrtM {margin:0; padding:0;
position:relative; background:url(../images/picpic.jpg) no-repeat
top left; height:479px; }
.mainconup .mmtoprt .mmrtM .mmrtA {margin:0; padding:200px 0
0 10px; position:relative; width:600px; }
.mainconup .mmtoprt .mmrtM .mmrtA .mmppr { float:right;
width: 195px; margin:0 0 0 -3px; padding:0; position:relative }
.mainconup .mmtoprt .mmrtM .mmrtA .mmppc {margin:0 195px 0 0;
padding:0; position:relative;}
.mainconup .mmtoprt .mmrtM .mmrtA .mmppc .mmppx {float:right;
width: 205px; margin:0; padding:0; position:relative}
.mainconup .mmtoprt .mmrtM .mmrtA .mmppc .mmppl {margin:0
205px 0 0; padding:0; position:relative; height:100px}
.bkspdC { font-size: 22px; font-weight:bold; color:#fff;
margin:0; padding:30px 0 0 0; position:relative; line-height:20px}
.bkspdB { font-size: 22px; font-weight:bold; color:#fff;
margin:0; padding:20px 0 0 0; position:relative; line-height:20px}
.bkspdA { font-size: 22px; font-weight:bold; color:#fff;
margin:0; padding:30px 0 0 10px; position:relative;
line-height:20px}
.mainconup .mmtoplt {margin:0 615px 0 0; padding:0;
position:relative }
.mainconup .mmtoplt .logo {margin:0; padding:2px 0 0 3px;
position:relative }
.mainconup .mmtoplt .linek {margin:10px 20px 7px 3px;
font-size:2px; padding:0; position:relative; border-top: #e7e7e7
2px solid }
.mainconup .mmtoplt .pargs {margin:0; padding:10px 20px 0
3px; position:relative; line-height:13px }
.hhllw { font-size: 22px; font-weight:bold; color:#23a9e8}
.maincentr { clear:both; margin:0; padding:0;
position:relative; background-color:#2774c2; display:block; }
.maincentr .mckbb {margin:0; padding:10px 10px 20px 20px;
position:relative; color:#fff; }
.maincentr .mckbb .mckrt {margin:0; padding:0;
position:relative; float:right; width:290px }
.maincentr .mckbb .mcklt {margin:0 290px 0 0; padding:0;
position:relative }
.maincentr .mckbb .mcklt .mcklrr {margin:0; padding:0;
position:relative; float:right; width:290px; height:170px;
background:url(../images/bgline.jpg) no-repeat right 10px; }
.maincentr .mckbb .mcklt .mcklcc {margin:0 290px 0 0;
padding:0; position:relative; height:170px;
background:url(../images/bgline.jpg) no-repeat right 10px; }
.maincentr .cbgc {margin:0; padding:0; position:relative;
background:url(../images/bgline2.gif) repeat-x top left;
height:2px; font-size:2px}
.customks {margin:0; padding:0; position:relative;
font-size:20px; font-weight:bold }
.quotep {margin:0; padding:20px 20px 0 0; position:relative }
.quotep .quotea {margin:0; padding:0; position:relative;
background:url(../images/qouteleft.jpg) no-repeat top left; }
.quotep .quotea .quoteb {margin:0; padding:0;
position:relative; background:url(../images/qouteright.jpg)
no-repeat bottom right }
.quotep .quotea .quoteb .quotez {margin:0; padding:28px 0 0
0; position:relative; font-size:12px; line-height:13px; }
.xquotep {margin:0; padding:20px 20px 0 20px;
position:relative }
.xquotep .xquotea {margin:0; padding:0; position:relative;
background:url(../images/qouteleft.jpg) no-repeat top left; }
.xquotep .xquotea .xquoteb {margin:0; padding:0;
position:relative; background:url(../images/qouteright.jpg)
no-repeat bottom right }
.xquotep .xquotea .xquoteb .xquotez {margin:0; padding:28px 0
0 0; position:relative; font-size:12px; line-height:13px; }
.mainbut {margin:6px 0 0 0; padding:0;
position:relative;clear:both; display:block }
.mainbut .mainbbj {margin:0; padding:0; position:relative }
.mainbut .mainbbj .mainbbrt {margin:0; padding:0;
position:relative; float: right; width: 167px }
.mainbut .mainbbj .mainbbrt .sshots {margin:0; padding:0 0
2px 0; position:relative; width: 167px }
.mainbut .mainbbj .mainbbrt .sshots .higfx {margin:0;
padding:0; position:relative; width: 167px; height:122px;
overflow:hidden }
.mainbut .mainbbj .mainbblt {margin:0 167px 0 0; padding:0;
position:relative }
.mainbut .mainbbj .mainbblt .mainbbrr {margin:0; padding:0;
position:relative; float: right; width: 425px }
.mainbut .mainbbj .mainbblt .mainbbrr .mainbbpads {margin:0;
padding:10px 26px 0 26px; position:relative; font-size:12px;
line-height:14px }
.mainbut .mainbbj .mainbblt .mainbbcc {margin:0 425px 0 0;
padding:0; position:relative; background:#3a3a3a; color:#fff }
.mainbut .mainbbj .mainbblt .mainbbcc .mainccpads {margin:0;
padding:20px 25px 25px 18px; position:relative; font-size:12px;
line-height:15px }
.hhllt { font-size: 20px; font-weight:bold; color:#23a9e8}
.hhllk { font-size: 18px; color:#23a9e8}
/* Main Part End */
/* Footer Part Start */
#footer {margin:0; padding:0; clear:both; position:relative;
display:block }
#footer .footboxbg {margin:0; padding:0; position:relative;
background: url(../images/index_18.jpg) repeat-x top left; }
#footer .footboxbg .footboxlt {margin:0; padding:0;
position:relative; background: url(../images/index_17.jpg)
no-repeat top left; }
#footer .footboxbg .footboxlt .footboxrt {margin:0;
padding:0; position:relative; background:
url(../images/index_20.jpg) no-repeat top right; height:36px }
/* Footer Part End */

Web Dynpro doesn't allow for the inclusion of custom HTML and CSS. It is far building business application in a client rendering abstracted framework.
If you need some common header, then you should consider the usage of the NetWeaver Portal.

Lists not showing in Design view

If I preview page in browser, I can see the bulleted list,
but it is not visibile in design view, pretty annoying. Anyone know
why this might be happening? I validated my code and got no
errors...

Open any html page
either type the element in code view, say h1. Hello
it doesn't show up in Design View (It's visible in Live view however)
Or,
In Design View type Hello (yes, it's visible!)
Highlight Hello, then right click (I use a 2 button mouse) select from the pop-up menu and format the hello as h1. Hello
It disappears from the design view... (yes, it's visible in Live View)
Menu spry's and other "widgets" inserted do not display correctly in Design View, but display Okay in Live view
(This behaviour did not happen in CS4)
Mo Eb , Garry
*** http://uofgts.com
** [email protected]
o "Beer is living proof that God loves us and wants us to be happy."
-Benjamin Franklin, American statesman and diplomat, (1706-1790 ).

PayPal buttons inside table scramble Design View in DW CS5.5

I developed my web site using Dreamweaver 8:
http://www.harmonize.com/hatleymusic/classic.html
As you see, I have PayPal buttons inside table cells. I did this using Design View, putting the insertion point in the table cell, going to code view, and pasting the PayPal button code at the insertion point. This all worked fine.
I just upgraded to DW CS5.5. and now when I try to use the same procedure, the Design View image gets scrambled after I paste the button code in code view. The table format is no longer in place, and I can no longer see where the cells of the table are. However, when I go to Live View, everything looks fine including the table and the buttons.
Can anyone tell me how to overcome this problem? As it stands, I cannot use DW to work on my web site, which is a major problem for me.
Thanks.

How do I get someone to respond to my question here?
Let me try again.
With DW CS5.5 when I try to insert a PayPal button into a table (which I always did with DW8) the table in Design View gets scrambled, making it unusable. Please would one of you out there who is much more knowledgeable about DW than me try it and see if there is a solution? If you create a new HTML page in Design view, create a table in it, place the insertion point inside one of the table cells, go to the code view and locate the insertion point there, then paste the PayPal button code at that point. Here's the code:
<form target="paypal" action="https://www.paypal.com/cgi-bin/webscr" method="post">
<input type="hidden" name="cmd" value="_s-xclick">
<input type="hidden" name="hosted_button_id" value="XSXQ9CUMUVLQC">
<input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_cart_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
<img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
</form>
Now go back to Design view and see how it looks. If it acts the way it does for me, the table is no longer visible, but if you go to Live View everything looks fine with the table and the button inside it. Of course, I can't design in Live View.
PLEASE can someone out there help me.
Many thanks.

Design view differs from browser view

When viewing in Design view my code correctly shows 2
overlapping rectangles. In browser view it shows two smaller
rectangles that do not overlap. I am using DW MX 2004. I have
attached small sample code.
Thanks,
Alexariel

DMX2004's Design view is not a browser, and can only
approximate (poorly)
how a page will look. The browser is always right. For
example, DMX2004 is
insensitive to the CSS error here -
div {width:250px; height:100;px; position:absolute; }
(note the ';' between '100' and 'px')
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Alexariel" <[email protected]> wrote in
message
news:gqh83o$kld$[email protected]..
> When viewing in Design view my code correctly shows 2
overlapping
> rectangles.
> In browser view it shows two smaller rectangles that do
not overlap. I am
> using
> DW MX 2004. I have attached small sample code.
> Thanks,
> Alexariel
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN"
> "
http://www.w3.org/TR/html4/loose.dtd">
> <html>
> <head>
> <title>Untitled Document</title>
> <meta http-equiv="Content-Type" content="text/html;
charset=iso-8859-1">
> <style type="text/css">
> body {margin: 0px; padding: 0px;}
> div {width:250px; height:100;px; position:absolute; }
> div.one {background-color:#FF0000; left: 0px; top: 0px;
> div.two {background-color:#00FF00;left: 75px; top:
25px;}
> </style>
> </head>
> <body>
> <div class="one">one</div>
> <div class="two">two</div>
> </body>
> </html>
>

CS3 loses css formatting in design view for non-templated pages

We recently upgraded to CS3. All of the pages on our site are
templated except the home page. The home page, when viewed in
design view in Dreamweaver, looks as if the css styles are missing.
Sometimes refreshing the view causes some of them to appear, but
not all. This didn't happen in the old version. And it's not
happening (so far) on our templated pages. Any ideas?

DW6x was not the sharpest knife in the drawer and would
tolerate lots of
things that DWCS3 will not.
I suggest you do the following -
* Change your doctype from this one (inserted by DMX6x, and
broken) -
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
to this one (valid and complete - the way DMX6x *should* have
done it) -
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN"
http://www.w3.org/TR/html4/loose.dtd">
Now your page will render in Standards mode, and not quirks
mode (a very bad
thing).
* Change this (in your stylesheet) -
vertical-align: top;
end FedFAQ
/* ********************** COLLAPSE/EXPAND MENUS
to this -
vertical-align: top;
/* end FedFAQ */
/* ********************** COLLAPSE/EXPAND MENUS
I am sure that by doing this you will see a remarkable change
in your
page....
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
==================
"abna" <[email protected]> wrote in message
news:f9fopl$it9$[email protected]..
>
http://dallasfed.org/index.cfm
>
> (tried to attach the code in the message, but kept
getting error messages
> from this site)

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

Similar Messages

Maybe you are looking for