2 Replies Latest reply on Sep 8, 2008 3:09 PM by Newsgroup_User

    browsers ignore property margins

    garnettehines
      I am not receiving any errors in browser compatibility check; the design view shows the established margins, but when previewed in browser main content is pressed up against the sidebar.

      site address: www.garnetteh.com

      Thanks for your help!
        • 1. Re: browsers ignore property margins
          Level 7
          Hello,

          Try adding the width of the sidebar (100px), which is floated, to the left
          margin value (70px) of the main content, like so:

          .twoColFixLtHdr #mainContent {
          margin: 0px 170px 0px 0px;
          }


          That's margin: top right bottom left values.

          Take care,
          Tim


          "garnettehines" <webforumsuser@macromedia.com> wrote in message
          news:ga45f0$rt3$1@forums.macromedia.com...
          >I am not receiving any errors in browser compatibility check; the design
          >view
          > shows the established margins, but when previewed in browser main content
          > is
          > pressed up against the sidebar.
          >
          > site address: www.garnetteh.com
          >
          > Thanks for your help!
          >
          > }
          > .twoColFixLtHdr #mainContent {
          > height: auto;
          > letter-spacing: normal;
          > margin-left: 70pt;
          > margin-right: 0px;
          > left: auto;
          > overflow: auto;
          > position: static;
          > bottom: auto;
          >


          • 2. Re: browsers ignore property margins
            Level 7
            garnettehines posted in macromedia.dreamweaver:

            > I am not receiving any errors in browser compatibility check; the
            > design view shows the established margins, but when previewed in
            > browser main content is pressed up against the sidebar.
            >
            > site address: www.garnetteh.com

            You've probably gotten your answer, but does it help if you delete this
            apparently redundant meta element?

            <meta name="" content="...>

            Other than it having an empty name attribute, it appears to be
            identical to your "keywords" meta.


            --
            Mark A. Boyd
            Keep-On-Learnin' :)