DW Live view looks OK, Browserlab doesn't

Hi there,
My webpage looks fine in Dreamweaver Live View, but not in Browserlab. For example, I created a block of text and formatted the font, headings and position, but it appears in Browserlab as if I had just typed it with no CSS rules applied.
I am on a Macbook Pro and using Dreamweaver version 11.5.
I get the same problem when checking all browsers. I tried refreshing several times and increasing the delay, but this had no effect.
Here is the URL for the page in Browserlab:
https://browserlab.adobe.com/en-us/index.html#browsers=WXPIE6000%2CWXPIE9000%2COSXFF7000%2 COSXSF5000%2CWXPCH14000;zoom=100;state=use;view=0;url=dreamweaver%3A%2F%2Fsite%3AHope%2520 Against%2520Hope%2FHAH_home.html;delay=5
Please help! Thanks.

Hi Charlie,
We can't repro your issue with pages we have. It's possible that it's something specific to your page, but we can't check that since you're doing local testing using DW. If you'd like us to give your page a try, you can package up the page and all the assets and send them to me at mrausch (at) adobe (dot) com
Thanks,
Mark

Similar Messages

  • Without changing anything: Live view looks fine, but "preview in browser" does not

    I haven't made any changes to our website in months. When I opened my index page, I did not change anything yet, but did a "preview in browser" and my whole slideshow is missing! It's still fine on the live website, as I haven't uploaded anything. Help.... why is it doing this? I need to add a small icon to our homepage, but I don't want to upload this page if it's not going to work!
    www.epaaudio.com

    On your page, these links are ALL root relative -
    <script language="JavaScript">
    // Advanced Random Images Start
    // Copyright 2001-2006 All rights reserved, by Paul Davis - www.kaosweaver.com
      var j,d="",l="",m="",p="",q="",z="",KW_ARI= new Array()
    // KW_rs[5000]
      KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/auditorium.jpg';
      KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/arena.jpg';
      KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/classroom.jpg';
      KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/conference.jpg';
      KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/conference2.jpg';
      KW_ARI[KW_ARI.length]='/Gallery_images/slideshow/courtrm.jpg';
      j=parseInt(Math.random()*KW_ARI.length);
      j=(isNaN(j))?0:j;
        document.write("<img name='randomSlideShow' src='"+KW_ARI[j]+"'>");
    function rndSlideShow(t,l) { // Random Slideshow by Kaosweaver
      x=document.randomSlideShow; j=l; while (l==j) {
        j=parseInt(Math.random()*KW_ARI.length); j=(isNaN(j))?0:j; }
      x.src=KW_ARI[j]; setTimeout("rndSlideShow("+t+","+j+")",t);
    rndSlideShow(5000,0)
    // Advanced Random Images End
    And, being embedded in JavaScript, they will not be found to be 'adjusted' by DW, even when using temporary files to preview.  I'm afraid you will have to just lump the fact that they are not displaying in preview mode.

  • Live View Window Reading Extra 20px

    Okay, I figured out what the bug is after the 13.1 update. On all of my live views on all of my projects and on both of my machines (I'm running Windows 8, btw), Dreamweaver is miscalculating the window width (or displaying the wrong window width in the corner) by 20px. So, if I have a media query that says don't break until a min-width of 801px, when I pull my Live View window out, it doesn't break until 821px.
    Where is this extra 20px coming from? It can't be in my stylesheets because this is happening in multiple projects on multiple devices.
    Is anyone else having this problem? If so, please respond.
    Anyone at Adobe listening to this?
    Cheers,
    Jonathan

    Okay. There are no errors in the code. I'm designing for a phone, so the "Preview in Browser" tool is worthless for me. I mean, I get it, because you can squish the browser down and all of that. But if I wanted to design sites that way, I'd get Notepad ++ and save myself the agony of paying thousands of dollars for the Adobe software suite.
    Now, I did uninstall DW 13.1, and reinstalled at 13.0 and the issue when away. I could actually use the Live View. Then, without thinking, I installed the update--and now the issue is back.
    All of that being said. I'm adding a photo of what my screen looks like and then I'm going to post ALL of the css, so there aren't any questions about what's going on. I've already gleened
    As I can see: horizontal scroll bar all the time. I've checked for every discrepency I can think of in my stylesheets: width: 100%, but margins: 0 5%; Padding blow out. All of it. I can't post the CSS here because it says I'd be violating the TOS.
    So, I'll post it up here: http://www.stpaulmedia.com/sample-style.css
    The Wordpress install I'm working on is locally hosted, so there's no point in trying to share that.

  • Live View not rendering CSS

    On  a Mac OS Mavefrick, DW CC.  Mostly working fine until recently.  Now CSS changes shown in Design View not seen in Live View.  Checked syntax, made changes in CSS Designer to no effect.  Could not uninstall DW CC (alias corrupted?) but reinstalled DW CC.  Re-install had no effect. Suggestions?
    RJL

    Thanks for your suggestion but this has been a sudden, recent change.  Never had this problem before using DW CC.
    Today, I tweaked the CSS and got to a point on one of my pages (calendar.htm) where everything in Design view and Live view looked just as I wanted it.  Tested in Firefox and Chrome, still fine.  Uploaded the file to the server, opened the page in Chrome, still fine. An hour or two later I went back to calendar.htm and whereas everything was fine in Design view the CSS styling on the h4 tags were not present in Live view.  Checked the web again and the calendar.htm looked as I expected it to look (serrakck.org --> Calendar).
    Still need help.  I have a bunch of CC apps on my Macs and maybe there is some comflick with them.  Don't have any other version of DW except DW CC.

  • CS5 logout in Live View

    Hi all,
    I've been playing with the new live view in CS5 on my Drupal site. Really great, powerful stuff. I did run into a problem though. I was able to login to my site in Live View, but I can't seem to log out. I've closed the page and closed Dreamweaver, but when I start Dreamweaver up again and open the index page, I'm still logged in. Is there a way to dump the session from within Dreamweaver? Any ideas?
    Thanks in advance.

    I'm not familiar enough with Drupal to know how you log out, but Live View works exactly like a browser, so you should be able to log out in the normal way. Don't forget that you need to hold down Ctrl/Cmd when clicking links or buttons in Live View.
    If that doesn't work, the simple way to log out is to use Preview in Browser. You should be able to log out from there. You're not logged into Dreamweaver, but into your local testing environment.

  • Webpage looks good with tranparent boxes and photo background in live view but not in browsers

    If anyone has time to help I would be very grateful.   I am new to dreamweaver and am trying to make a webpage with transparent colums and boxed text using styles.  It looks perfect in "live view" but when I look at it in any browser all formatting is gone.  It looks like the background with text on top layed out wrapped across the entire page.   I have not been able to figure out what is wrong in days of searching.  Does anyone know the answer?
    This first the format I want and is what it looks like in Live View, the second is what it looks like in most browsers.
    Here is the code I used:
    </style>
    <link href="../styles/tcastyles.css" rel="stylesheet" type="text/css">
    <style type="text/css">
    body {
              background-image: url(bamboo.JPG);
              margin-left: 150px;
    a:link {
              color: #600;
              text-decoration: none;
    a:visited {
              text-decoration: none;
    a:hover {
              text-decoration: none;
    a:active {
              text-decoration: none;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 12px;
              font-weight: bold;
    a {
              font-size: 12px;
    body,td,th {
              font-family: Verdana, Geneva, sans-serif;
    .container .faqs h2 {
              line-height: 40px;
    .container .faqs ul li {
              text-align: left;
    .footer {
              padding: 5;
              position: relative;
              clear: both;
    </style>
    <div class="container">
      <div class="header"><span class="menutable"></span><img border="0" src="navigate_projects.jpg" width="307" height="167" usemap="#FPMap0" alt="The Conservation Agency - Project Menu" align="absmiddle" />
        <map name="FPMap0">
          <area shape="rect" coords="132, 112, 172, 127" href="asia.htm" alt="Asia" />
          <area shape="rect" coords="138, 92, 286, 110" href="west.htm" alt="Western Hemisphere" />
          <area shape="rect" coords="138, 73, 279, 89" href="flamingos.htm" alt="British Virgin Islands" />
          <area shape="rect" coords="131, 55, 249, 72" href="turkscaicos.htm" alt="Turks and Caicos" />
          <area shape="rect" coords="121, 35, 244, 52" href="newengland.htm" alt="Narragansett Bay" />
          <area shape="rect" coords="103, 17, 306, 32" href="coyote.htm" alt="Narragansett Bay Coyote Study " />
          <area shape="rect" coords="121, 128, 173, 144" href="pacific.htm" alt="Pacific" />
        </map>
      </div>
      <div class="menu">
        <table width="100%" border="0" align="center" id="menutable">
          <tr>
            <td height="30" align="center" valign="middle"><p><strong><a href="mission.htm">Mission</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="pubs.htm">Publications</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="projects.htm">Projects</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="opps.htm">Opportunities</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="sponsors.htm">Sponsors</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="coyote.htm">NBCS</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="guana.htm">Guana</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="tca.htm">Contact us</a></strong></p></td>
            <td height="30" align="center" valign="middle"><p><strong><a href="index.htm">Home</a></strong></p></td>
          </tr>
        </table>
      </div>
      <div class="banner">Narragansett Bay Coyote Study</div>
      <d/div>
          <div class="box739">
            <h3>What does NBCS Do?</h3>
            <p>Since 2004 The Narragansett Bay Coyote Study (NBCS) has been developing science-based coexistence and management strategies for our newest top predator.  Coyotes, originally a prairie species, have successfully colonized all parts of the continental and nearshore us in the past 100 years. They reached the islands of Narragansett Bay in the mid-1990s. Since then coyotes have become increasingly abundant and problematic in some island communities.</p>
            <p>In our history of cohabitation with coyotes people consistently  tried to eliminate them by hunting, trapping, and poisoning. Lethal removal  worked for individual problem animals but did not work as a population control strategy. Why? Coyotes have intrinsic physiological and behavioral abilities to control their own numbers. If coyotes are removed they increase reproduction and numbers rapidly rebound. The critical population regulation trigger is competition for food. As long as coyotes are well fed (with few coyotes competing for food) their populations will grow. </p>
            <p>It is also known that opposite effect occurs if coyotes if coyotes are stressed by competition for food. If there are too many coyotes competing for the food available coyotes will drop the the level sustainable by those resources.</p>
            <p>Understanding this relationship, NBCS scientists decided to study the resource use of coyotes on two islands in Narragansett Bay, Rhode Island. We used GPS tracking collars to find out where the coyotes were spending thier time. We theorized that if we could identify important coyote food resources - and control them - the coyotes would bring their own numbers down. NBCS calls this &quot;passive coyote management.&quot;</p>
            <p> Since 2005 when we trapped and collared our first island coyotes we have continually found that the most important food resources to our study are provided by people. That means they are within our control That means we can control coyotes. If we remove anthropogenic resources (human subsidies) coyote numbers will drop to the level sustainable by natural resources. When coyotes are sustained only by natural prey (mice, woodchucks, rabbits, geese, and deer) coyotes numbers will be lower and they will provide helpful pest control services. </p>
            <p>Based our scientific data NBCS generated a set of <a href="coyotes/Best Management Practices for Coexistence with Coyotes - Nov 8 2010.pdf" target="_new">Best Management Practices for Coexistence with Coyotes</a>- basically a toolbox for safe, sustainable, community coyote management. We are working with the towns in our study area to adopt the CBMPs and be the first community in the nation to successfully and sustainably manage coyotes. We also believe other cities and towns might be able to use our results as a template if they are experiencing coyote problems. We have only just begun to implement the CBMPs on our islands. We hope in the near future to have all our towns implementing the CBMPs - only then will we see the full impacts they make on coyote numbers and behavioral problems. You can follow our progress on this website.</p>
          </div>
          <div class="footer">
            <table width="100%" border="0" cellspacing="5">
              <tr>
                <td>Return to top</td>
                <td><a href="mailto:[email protected]">[email protected]</a></td>
              </tr>
            </table>
          </div>
        </div>
      </div>
      <p> </p>
    </div>iv class="faqs">
        <h2>FAQs</h2>
        <ul>
          <li>How do coyotes control their own population numbers?</li>
          <li>bla bla bla</li>
        </ul>
      </div>
      <div class="content">
        <div class="clearbox">
          <div class="col1">
            <h3>Middletown Adopts the CBMPs and passes a No-Feeding Ordinance!</h3>
          </div>
          <div class="col2">
            <h3>Pilot, Java, and the Valley Pack</h3>
          <
    And here are the styles:
    .container {
              height: 1500px;
              width: 975px;
              border: 8px solid #660000;
              float: left;
    .header {
              float: left;
              height: 170px;
              width: 975px;
              background-color: #033000;
    .menu {
              background-color: #FFC;
              float: left;
              height: 30px;
              width: 975px;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 9px;
              color: #660000;
              font-weight: bold;
              margin-bottom: 5px;
    .table {
              font-family: Verdana, Geneva, sans-serif;
              font-size: 8px;
              font-weight: bold;
    .banner {
              float: left;
              height: 100px;
              width: 739px;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 37px;
              font-weight: bold;
              color: rgba(0,51,0,1);
              background-color: rgba(255,255,204,.7);
              text-align: center;
              line-height: 75px;
              border-radius: 5px;
              padding: 5px;
              margin: 5px;
    .clearbox {
              float: left;
              height: auto;
              width: 760px;
    .box739 {
              width: 739px;
              float: left;
              height: auto;
              background-color: rgba(255,255,204,.7);
              font-size: 12px;
              color: rgba(0,51,0,1);
              border-radius: 5px;
              padding: 5px;
              margin: 5px;
    .faqs {
              float: right;
              height: 620px;
              width: 205px;
              font-family: Verdana, Geneva, sans-serif;
              font-size: 12px;
              font-style: normal;
              line-height: normal;
              overflow: scroll;
              background-color: rgba(255,255,204,.7);
              margin: 5px;
              border-radius: 5px;
              font-weight: bold;
              color: rgba(0,51,0,1);
              text-align: center;
    .col1 {
              float: left;
              height: 500px;
              width: 359px;
              background-color: rgba(255,255,204,.7);
              font-size: 12px;
              border-radius: 5px;
              color: rgba(0,51,0,1);
              margin: 5px;
              padding: 5px;
    .col2 {
              float: left;
              height: 500px;
              width: 359px;
              background-color: rgba(255,255,204,.7);
              font-size: 12px;
              border-radius: 5px 5px 5px 5px;
              color: rgba(0,0,0,1);
              padding: 5px;
              margin: 5px;
    .footer {
              position:relative;
              clear: both;
              background-color: rgba(255,255,204,1);
              font-size: 12px;
              color: rgba(0,51,0,1);

    Helo thanks for responding .  I think it uploads...  It says it does as an assocaiated file when I put to the website.  But that sounds like it is the issue. Those format commands seem to be the one it is ignoring.  I am not familiar with html but I see that the href command is what identifies the path to the file I call TCAStyles.  I notice that dw puts all my files in a local public file and the structure is different - with no public file - at the site.
    I am not sure what the 2 dots in the href command mean - there is not a full path.  Is this command valid?  I will try to look into the directory structure on local and remote site and will check for files.

  • When using Live View, site looks great, browser testing goes crazy

    I am creating a new website (and I am really unexperienced with Dreamwaver CS5).  But when I check my site using "Live View" everything looks great, the way it is supposed to.  Then when I go to test it in my browswer (Primary browser is Chrome) it goes crazy:  I at first noticed that I had saved one copy as an .asp but then resaved it to .xhtml  I did delete the first line of code already that the .asp file created as it kept giving me an error on line 1.
    Then I tried to do a spry drop-down menu bar, which I have deleted since I thought I was doing something wrong with that and I should just stick to what I half-way know.
    If I were to preview the template page it gives me this error:
    This page contains the following errors:
    error on line 150 at column 76: error parsing attribute name
    Below is a rendering of the page up to the first error.
    Here is line 150:
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    If I were to test the index.xhtml page in the browser, it ignores most images (all but one), and the first nav-bar (an editable region) appears to the left instead of under the header.  The layout is totally ignored and everything is on the left-hand side of the screen instead of in a two column layout.
    I am not testing this on a server just off of my computer.
    I am assuming that the error has something to do with the .asp file I first did and when I resaved it, since I don't know what I would be looking for, is still in there screwing it up.
    Here is the code from the template page:
    <!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>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Midwest Window Brokers | Page</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    <style type="text/css">
    <!--
    body {
              font: 100%/1.4 Verdana, Arial, Helvetica, sans-serif;
              margin: 0;
              padding: 0;
              color: #000;
              background-image: url(/images/bkg.jpg);
              background-repeat: repeat;
    /* ~~ Element/tag selectors ~~ */
    ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
              padding: 0;
              margin: 0;
    h1, h2, h3, h4, h5, h6, p {
              margin-top: 0;           /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
              padding-right: 15px;
              padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
              text-align: left;
    a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
              border: none;
    /* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
    a:link {
              color: #060;
              text-decoration: none; /* unless you style your links to look extremely unique, it's best to provide underlines for quick visual identification */
    a:visited {
              color: #666;
              text-decoration: underline;
    a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
              text-decoration: none;
    /* ~~this fixed width container surrounds the other divs~~ */
    .container {
              width: 960px;
              background: #FFF;
              margin: 0 auto; /* the auto value on the sides, coupled with the width, centers the layout */
    /* ~~ the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo ~~ */
    .header {
              background-color: #FFF;
    /* ~~ These are the columns for the layout. ~~
    1) Padding is only placed on the top and/or bottom of the divs. The elements within these divs have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the *total* width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
    2) No margin has been given to the columns since they are all floated. If you must add margin, avoid placing it on the side you're floating toward (for example: a right margin on a div set to float right). Many times, padding can be used instead. For divs where this rule must be broken, you should add a "display:inline" declaration to the div's rule to tame a bug where some versions of Internet Explorer double the margin.
    3) Since classes can be used multiple times in a document (and an element can also have multiple classes applied), the columns have been assigned class names instead of IDs. For example, two sidebar divs could be stacked if necessary. These can very easily be changed to IDs if that's your preference, as long as you'll only be using them once per document.
    4) If you prefer your nav on the left instead of the right, simply float these columns the opposite direction (all left instead of all right) and they'll render in reverse order. There's no need to move the divs around in the HTML source.
    .sidebar1 {
              float: right;
              width: 300px;
              background: #ffffff;
              padding-bottom: 10px;
    .content {
              padding: 10px 0;
              width: 650px;
              float: right;
    /* ~~ This grouped selector gives the lists in the .content area space ~~ */
    .content ul, .content ol {
              padding: 0 15px 15px 40px; /* this padding mirrors the right padding in the headings and paragraph rule above. Padding was placed on the bottom for space between other elements on the lists and on the left to create the indention. These may be adjusted as you wish. */
    /* ~~ The navigation list styles (can be removed if you choose to use a premade flyout menu like Spry) ~~ */
    ul.nav {
              list-style: none; /* this creates the space between the navigation on the content below */
    ul.nav li {
              border-bottom: 1px solid #666; /* this creates the button separation */
    ul.nav a, ul.nav a:visited { /* grouping these selectors makes sure that your links retain their button look even after being visited */
              padding: 5px 5px 5px 15px;
              display: block; /* this gives the link block properties causing it to fill the whole LI containing it. This causes the entire area to react to a mouse click. */
              width: 160px;  /*this width makes the entire button clickable for IE6. If you don't need to support IE6, it can be removed. Calculate the proper width by subtracting the padding on this link from the width of your sidebar container. */
              text-decoration: none;
              background-color: #DDDECB;
    ul.nav a:hover, ul.nav a:active, ul.nav a:focus { /* this changes the background and text color for both mouse and keyboard navigators */
              background: #ADB96E;
              color: #FFF;
    /* ~~ The footer ~~ */
    .footer {
              padding: 10px 0;
              position: relative;/* this gives IE6 hasLayout to properly clear */
              clear: both; /* this clear property forces the .container to understand where the columns end and contain them */
              background-color: #DDDECB;
              font-size: small;
    /* ~~ miscellaneous float/clear classes ~~ */
    .fltrt {  /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
              float: right;
              margin-left: 8px;
    .fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
              float: left;
              margin-right: 8px;
    .clearfloat { /* this class can be placed on a <br /> or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
              clear:both;
              height:0;
              font-size: 1px;
              line-height: 0px;
    #h-navbar {
              font-weight: bold;
              height: auto;
              font-size: 18px;
              line-height: 50px;
              background-image: url(/images/navbar2.jpg);
    #h-navbar1 {
              background-image: none;
              background-repeat: repeat-x;
    -->
    </style>
    <script type="text/javascript">
    function MM_preloadImages() { //v3.0
      var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
        var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    function MM_swapImgRestore() { //v3.0
      var i,x,a=document.MM_sr; for(i=0;a&&i<a.length&&(x=a[i])&&x.oSrc;i++) x.src=x.oSrc;
    function MM_findObj(n, d) { //v4.01
      var p,i,x;  if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) {
        d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);}
      if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n];
      for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document);
      if(!x && d.getElementById) x=d.getElementById(n); return x;
    function MM_swapImage() { //v3.0
      var i,j=0,x,a=MM_swapImage.arguments; document.MM_sr=new Array; for(i=0;i<(a.length-2);i+=3)
       if ((x=MM_findObj(a[i]))!=null){document.MM_sr[j++]=x; if(!x.oSrc) x.oSrc=x.src; x.src=a[i+2];}
    </script>
    </head>
    <body onload="MM_preloadImages('/images/home2.jpg')">
    <div class="container">
      <div class="header"><a href="/index.xhtml"><img src="../images/heading.jpg" alt="Midwest Window Brokers, Windows, Siding, Roofing, 605-791-5352" name="Insert_logo" width="950" height="200" align="right" id="Insert_logo" style="background: #FFFFFF; display:block;" /></a>
        <div id="h-navbar1"><a href="/index.xhtml"><img src="/images/home.jpg" alt="home" width="159" height="51" id="Image1" onmouseover="MM_swapImage('Image1','','/images/home2.jpg',1)" onmouseout="MM_swapImgRestore()" /></a><a href="/windows.html"><img src="/images/services.jpg" width="151" height="51" alt="services" /></a><a href="/freebay.xhtml"><img src="/images/specials.jpg" width="153" height="51" alt="specials" /></a><a href="/gallery.html"><img src="/images/gallery.jpg" width="152" height="51" alt="gallery" /></a><a href="/roofing.xhtml"><img src="/images/order.jpg" width="152" height="51" alt="order" /></a><img src="/images/blank.jpg" width="75" height="51" /><img src="/images/facebook.jpg" width="38" height="51" alt="facebook" longdesc="http://facebook.com/midwestwindowbrokers" /><img src="/images/twitter.jpg" width="37" height="51" alt="twitter" longdesc="http://twitter.com/midwestwindow" /><img src="/images/google.jpg" width="42" height="51" alt="google+" longdesc="http://https://plus.google.com/u/0/b/108071947231835835141/108071947231835835141/posts" /></div>
      <!-- end .header --></div>
      <!-- TemplateBeginEditable name="navbar" -->
      <div id="h-navbar">
        <div id="h-navbar2">  Content for  id "h-navbar2" Goes Here</div>
      </div>
      <!-- TemplateEndEditable -->
      <div class="sidebar1">
        <ul class="nav">
        </ul>
        <p> <div id="wufoo-z7x3k1">
    Fill out my <a href="http://midwestwindow.wufoo.com/forms/z7x3k1">online form</a>.
    </div>
    <script type="text/javascript">var z7x3k1;(function(d, t) {
    var s = d.createElement(t), options = {
    'userName':'midwestwindow',
    'formHash':'z7x3k1',
    'autoResize':true,
    'height':'601',
    'async':true,
    'header':'show'};
    s.src = ('https:' == d.location.protocol ? 'https://' : 'http://') + 'wufoo.com/scripts/embed/form.js';
    s.onload = s.onreadystatechange = function() {
    var rs = this.readyState; if (rs) if (rs != 'complete') if (rs != 'loaded') return;
    try { z7x3k1 = new WufooForm();z7x3k1.initialize(options);z7x3k1.display(); } catch (e) {}};
    var scr = d.getElementsByTagName(t)[0], par = scr.parentNode; par.insertBefore(s, scr);
    })(document, 'script');</script></p>
        <!-- end .sidebar1 --></div>
      <!-- TemplateBeginEditable name="Body" -->
      <div class="content">
        <h1>Instructions</h1>
        <p>Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the fixed layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - <a href="http://www.adobe.com/go/adc_css_layouts">http://www.adobe.com/go/adc_css_layouts</a>.</p>
        <h2>Clearing Method</h2>
        <p>Because all the columns are floated, this layout uses a clear:both declaration in the .footer rule.  This clearing technique forces the .container to understand where the columns end in order to show any borders or background colors you place on the .container. If your design requires you to remove the .footer from the .container, you'll need to use a different clearing method. The most reliable will be to add a &lt;br class=&quot;clearfloat&quot; /&gt; or &lt;div  class=&quot;clearfloat&quot;&gt;&lt;/div&gt; after your final floated column (but before the .container closes). This will have the same clearing effect.</p>
        <h3>Logo Replacement</h3>
        <p>An image placeholder was used in this layout in the .header where you'll likely want to place  a logo. It is recommended that you remove the placeholder and replace it with your own linked logo. </p>
        <p><span style="font-size: 18px; color: #C00; font-weight: bold; font-style: italic;">Logo Replacement</span></p>
        <p> Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes. </p>
        <p>To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)</p>
        <h4>Backgrounds</h4>
        <p>By nature, the background color on any div will only show for the length of the content. This means if you're using a background color or border to create the look of a side column, it won't extend all the way to the footer but will stop when the content ends. If the .content div will always contain more content, you can place a border on the .content div to divide it from the column.</p>
        <!-- end .content -->
      </div>
      <!-- TemplateEndEditable -->
      <div class="footer">
        <p class="footer"><strong>  <em>References Available!</em>     We accept cash, check, Visa, Discover, MasterCard</strong></p>
          Copyright 2012 Midwest Window Brokers Inc. All Rights Reserved.
        <!-- end .footer --></div>
      <!-- end .container --></div>
    </body>
    </html>

    I had saved one copy as an .asp but then resaved it to .xhtml 
    I'm assuming this is a static web site.  Rename (F2) all your pages with .html or .htm extension. 
    .xhtml is not a valid extension.
    Nancy O.

  • Why page looks fine in Design view but not live view?

    I am new to DW. I created a page that looks fine in design view but now I cant get it to show up in live view or the browser preview. Can some one give me some areas to troubleshoot. Most of the code is from a previous page I created that still looks fine in every view. I am not sure what I could be doing different in setting up this site.

    Thanks for taking the time to reply to question. Aftr taking a break. I came back realized I inserted the stylesheet before I changed site settings. I just needed to remove the forward slash from my stylesheet declaration. FYI for anyone else new to DW: if stuffs not showing  in Live View and Browser Preview eg background images, Go to Manage Sites and check your site setting for Links relative to: You may have switched between document and site root. Thus breaking your links to images or in my case the entire style sheet.

  • Why does my page look great in design view and to the left in live view?

    I just created a new page using a fluid grid layout and in "design" view it looks great but in "live" view or on a browser preview the wording all goes to the left.  What I am doing wrong?  I also have another question which may relate to the first.  I  have four templates. Do I create a new named .css file for each new template or continue using the same layout.css file for all templates? Since I created a new .css file for every template maybe it is causing confusion.  Thanks in advance.

    If this is what you want, rework your HTML so all three images are in the same div and adjust your css to  narrow the scroll down image and on Order jpg, vertically align top, 30px margin.
    <div id="header">
    <div id="pic1">
    <img src="Thumbs/Scroll-Down.jpg" alt="More Pictures">
    <img class="goldborder" src="NewImages/englilshivymain.jpg" alt="">
    <a href="#OrderHere2">
    <img alt="Order Here" src="Thumbs/OrderHere.jpg">
    </a>
    <br>
    English Ivy (Detail)
    </div>
    <div id="pic4">

  • Results look different in Live View and Browser Lab

    I'm using CS5 and am using absolute positioning to place an image. It looks great in Live View, but when I open Browser Lab it has shifted dramatically. Any ideas what's going on and with view should I trust. Thanks.

    Hi Jalynoble,
    We've tried to repro the issue you describe, but haven't been able to, so it must be something specific to your page. Can you provide us with a URL or package up and email the source code for the page with this issue so we can look into it?
    You can post the url here, or email the files to [email protected]
    Thanks,
    Mark

  • Spry Menu bar looks OK in Live View, not browser

    I'm trying to insert a Spry menu bar in an existing site to replace one previously built with an F-source product. There is a Flash movie above the menu bar. It looks fine in Live View, but when I look at it in a browser, it expands to about ten times its height with only the last menu item visible (out of nine). It also displaces the Flash movie to the left and up. Any idea what's causing this, and how to fix it? Thanks for any help you can provide!
    Live View:
    Browser View:

    Thanks for your help. I tried to add the code above the menu bar (you didn't specify whether to add before the body tag) but it didn't help in either location.
    I've uploaded the page in question to the site. You can access the page via http://www.acsi-cybersa.com/index2.html
    If you back up to the "www.acsi-cybersa.com" URL, you will see a working homepage with an f-source menu that is acting a bit squirrely, and which I am trying to replace with the Spry menu. The URL above "index2.html" is the working replacement for the home page.
    If you can figure out what's happening with the Spry menu and how to fix it, I would be eternally grateful.
    Thanks, Dan

  • Why doesn't Auto Suggest work in IE but works in Live View?

    Hi, In Dreamweaver CS5 I have created a simple test page for the Auto Suggest widget using a second page containing the data in an HTML table.  The Auto Suggest works perfectly when viewed in the Dreamweaver Live View and Multi Screen View. However, when i view the test page in IE8 the widget doesn't work and there is the small 'Done' with the yellow triangle and exclamation mark in the bottom left indicating a script error.
    Any ideas what's the problem - presumably with IE?
    Thanks

    Thanks.  I have posted the test page to
    www.bpmac.co.uk/test.asp
    I would be happy to receive a link to a sample that works.
    Regards
    Phillip

  • Page looks fine in live view but not fine in safari

    my index.html page looks okay in live view, but when i open it in safari some of my text is unformated. My CSS page is correct so the problem lies in my code. I have attached the html file, any help will be appreciated. Thank you!

    Thanks for taking the time to reply to question. Aftr taking a break. I came back realized I inserted the stylesheet before I changed site settings. I just needed to remove the forward slash from my stylesheet declaration. FYI for anyone else new to DW: if stuffs not showing  in Live View and Browser Preview eg background images, Go to Manage Sites and check your site setting for Links relative to: You may have switched between document and site root. Thus breaking your links to images or in my case the entire style sheet.

  • My Live view doesn't work, it can't 'find my server'. But my server is connected and working. Why?

    Hi,
    I am confused as to why my live view can't connect to my server. However I have successfully connected to my server outside of the live view and uploaded my website.
    I am new to dreamweaver, and I trying to learn to build a wordpress site from sractch. This is the error message I get:
    The page "http://ftp.stoneinyrshoe.co.uk/index.php" was not loaded because Dreamweaver could not find the server "ftp.stoneinyrshoe.co.uk". Please make sure you are connected to the internet and the server name is correct.
    When I direct Live view (testing) to use the same site details as my main connection, it still doesn;t work.
    Any advice would be much appreciated.
    Thanks

    That's an FTP address you are trying to connect do.  That's different from the regular HTTP protocol.  From the address you posted I'm wondering if you have installed MAMP/WAMP for a local server on your machine or if this testing server is separate from the actual domain serving the pages.  Can you explain your setup a little more?

  • Problem: design view looks completely different than live view

    I am trying to make changes to my home page in Dreamweaver, and when I am viewing the page in 'design view' the background image for the container is missing, and the divs are all over the place. When I view the same page in live view and in browser preview, it looks fine.
    Because I can't really see what the page is going to look like in 'design view', I can't really make changes to the site. Any help would be much appreciated.
    Link to screenshot of 'design view'  
    www.simply-eden.com/images/screenshot1.tiff
    Link to screenshot of 'live view'       
    www.simply-eden.com/images/screenshot2.tiff
    link for purpose of viewing the code only
    www.simply-eden.com/images/index.html
    Thanks for the help.

    When things get really goofed up, it could be caused by malformed code or orphaned div tags.  Sometimes browsers will let you slide with poor code, but DW Design View won't.
    Use these online code validation tools and fix any reported errors.
    HTML Validator - http://validator.w3.org 
    CSS Validator - http://jigsaw.w3.org/css-validator/  
    HTML & CSS Tutorials - http://w3schools.com/
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists
    www.alt-web.com/
    www.twitter.com/altweb
    www.alt-web.blogspot.com

Maybe you are looking for