.clearfix css doesnt render in DW Design View

I have used the css .clearfix code in my site to enable two
divs to clear a floated element. It works fine in browsers like
IE6, IE7, FF, Safari, etc. But the clearfix code doesnt make the
divs clear when I am designing in Dreamweavers Design View. They do
not clear. I have to use <br style="clear:both;"/> after the
two divs to make them clear in Design View.
The problem is that actually adding <br
style="clear:both"/> after the two divs in DW renders the
.clearfix solution redundant as it has the same effect of clearing
the float.
Basically Im saying its a shame that the excellent .clearfix
code doesnt render in Desing View. Or does anyone know how to make
it render in Design View without using the <br style... code?
.clearfix:after {
content:".";
display:block;
height:0;
clear:both;
visibility:hidden;
.clearfix {display:inline-block;}
/* Hide from IE Mac \*/
.clearfix {display:block;}
/* End hide from IE Mac */

Hi there, in case anybody comes across this issue again, I had the same prob, compounded by 'edge case' situations where the .clearfix class wasn't enough. A solution (not ideal, but it does solve the problem) can be found here:
http://forums.adobe.com/message/130568#130568
It involves using a float clearance CSS technique, and then adding markup to enforce clearance in Design Mode, as suggested by Billy - the differnce is that you also set line-height and height styles to 0px on the added markup. I know adding markup is hardly ideal, but I added an alt="PLACEHOLDER" attribute to my markup clearance div (or <br /> in Billy's case), so I could 1) search and replace it out it later and 2) generate a validation error so I definately wouldn't miss it.
-d

Similar Messages

  • CSS Changes not showing in Design View

    I'm just coming over from GoLive (and their layout grid) so
    I'm not entirely familiar with DreamWeaver CS3 and CSS.
    However, whenever I make changes in a CSS sheet (and save
    them) they are not immediately rendered in the Design View. They
    show up just fine if I "Preview in Browser" though. I can even
    close the html page and reopen it and sometimes they will show up,
    but not usually. Oh, and the "Refresh Design View" button is greyed
    out and doesn't do anything.
    Thanks,
    Dan

    Yes, that seems to be the case. I ran a validation check on
    the html page (it was coded in XHTML 1.0 strict) and came up with 2
    errors related to the CSS features I was trying to use.
    Thanks!

  • CSS is not showing in design view

    Hello, I wonder if anyone can help. I would appreciate very
    much if you can... I have read all the css related problems, but
    did not see the problem I am having.
    Anyway, I have done a website template for someone and I gave
    it to him to update the contents. However, on his dreamweaver
    Design view, the css does not support it at all so it looks all
    messy. Though when he preview it on IE, this is all fine. I have
    made templates and css files with dreamweaver and I can view
    everything fine. He seems to have the same version of DW (MX 2004)
    so I am not sure how this happens. We were looking in everything
    (including goofy css as someone says on this forum), but have no
    luck so far. Here is my link and I pasted my css here.
    http://www.norithefish.com/index2.html
    Many thanks for this.
    Noriko
    /* HTML tag styles */
    body
    {background: #cccccc; font-family: Verdana, Arial, Helvetica,
    sans-serif;
    font-size: small; color: #000000; font-weight: normal}
    a { color: #333333; text-decoration: none }
    a:active { color: #666666; text-decoration: none }
    a:hover { color: #CC3300; text-decoration: underline }
    .bodytext { font-size: small; color: #000000; font-weight:
    normal}
    .smalltext { font-size: x-small; color: #000000; font-weight:
    normal}
    .smalltextw { font-size: x-small; color: #ffffff;
    font-weight: normal}
    .title{ font-size: 1.5em; font-weight: bold; color: #CC3300}
    .wbracket{ font-size: small; font-weight: normal; color:
    #ffffff}
    .smalltitle { font-size: 1em; font-weight: normal; color:
    #666666}
    .sub { font-size: small; font-weight: bold; color: #ffffff }
    .foot { font-size: x-small; font-weight: normal; color:
    #000000}
    h1 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 1.5em;
    color: #cc3300
    h2 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 1.15em;
    color: #cc3300
    h3 {
    font-family: Verdana, Arial, Helvetica, sans-serif;
    font-size: 1em;
    color: #666666
    ul{
    list-style-type: square;
    ul ul{
    list-style-type: disc;
    ul ul ul{
    list-style-type: none;
    /* Layout Divs */
    #pageNav{
    float: left;
    width:21.3%;
    top:10px;
    padding-left: 0px;
    border-bottom: 1px solid #cccccc;
    border-right: 1px solid #cccccc;
    #content{
    width:75%;
    float: left;
    padding: 0px 0px 0px 0px;
    margin: 0px 0px 1px 20px;
    /* Component Divs */
    #siteName{
    margin: 0px;
    padding: 16px 0px 8px 0px;
    color: #ffffff;
    font-weight: normal;
    /************** feature styles *****************/
    .feature{
    padding: 0px 0px 0px 0px;
    font-size: 100%;
    /************* #siteInfo styles ***************/
    #siteInfo{
    clear: both;
    font-size: 100%;
    background-color: #999999;
    padding: 0px 0px 0px 0px;
    border-top: 1px solid #666666;
    /************* #smalltitle styles ***************/
    #smalltitle{
    clear: both;
    background-color: #ffffff;
    font-size: 100%;
    padding: 0px 0px 0px 0px;
    border-top: 1px solid #CC3300;
    border-bottom: 1px solid #CC3300;
    /*********** #sectionLinks styles ***********/
    #sectionLinks{
    position: relative;
    width: 150px;
    margin: 0px;
    padding: 0px;
    border-bottom: 1px solid #cccccc;
    font-size: 90%;
    #sectionLinks a:link{
    font-size: 1.15em;
    padding: 2px 0px 5px 10px;
    border-top: 1px solid #cccccc;
    width: 100%;
    width: auto;
    #sectionLinks a:visited{
    font-size: 1.15em;
    border-top: 1px solid #cccccc;
    padding: 2px 0px 5px 10px;
    #sectionLinks a:hover{
    font-size: 1.15em;
    border-top: 1px solid #cc3300;
    background-color: #dddddd;
    padding: 2px 0px 5px 10px;
    /*********** .frame styles ***********/
    .frame {
    width: 700px;
    left: 50%;
    padding-top: 0px;
    margin-left: -350px;
    margin-top: 0px;
    position: absolute;
    visibility: visible;
    border-top: 1px solid #999999;
    border-bottom: 1px solid #999999;
    border-right: 1px solid #999999;
    border-left: 1px solid #999999;
    background-color: #ffffff;
    .bg {
    height: 1px;
    background-color: #cccccc;
    width: 100%;
    /*********** #pageNav link styles ***********/
    #pageNav ul a:link, #pageNav ul a:visited {display: block;}
    #pageNav ul {list-style: none; margin: 0; padding: 0;}
    /* hack to fix IE/Win's broken rendering of block-level
    anchors in lists */
    #pageNav li {border-bottom: 1px solid #EEE;}
    /* fix for browsers that don't need the hack */
    html>body #pageNav li {border-bottom: none;}
    /********************* end **********************/

    > *** you are missing <li> at the beginning of the
    line and </li> at the end
    > or you want to remove the </li> from the previous
    lines.
    Or move the image within the existing pair. You cannot have
    that
    construction, though -
    <li>blah</li>
    <img>
    <li>blah</li>
    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
    ==================
    "josie1one" <[email protected]> wrote in message
    news:[email protected]...
    > It sounds to me as if it's a path issue.
    > Your path is this:
    > <link rel="stylesheet" href="styles/inside.css"
    type="text/css">
    >
    > Does he have a folder called "styles" within which
    should be the
    > stylesheet?
    >
    > You have a couple of code problems (I'd say unrelated to
    your question).
    > <li><a href="1-about.html">Order your Tshirt
    </a></li>
    > <img src="ferrari_team_polo.jpg" alt="photo of a
    T-shirt" width="120"
    > height="180">***
    > <li><a href="1-about.html">Order your
    cap</a></li>
    > <img src="ferrari_cap.jpg" alt="photo of a cap"
    width="120"
    > height="75"><br>***
    >
    > *** you are missing <li> at the beginning of the
    line and </li> at the end
    > or you want to remove the </li> from the previous
    lines.
    >
    > and according to
    >
    http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.norithefish.com%2Findex2.html
    >
    > you have an extra </div> a couple of lines above
    the </body>
    >
    >
    > --
    > Jo
    >
    >
    >
    >
    >
    > "norithefish" <[email protected]> wrote
    in message
    > news:[email protected]...
    >> Hello, I wonder if anyone can help. I would
    appreciate very much if you
    >> can...
    >> I have read all the css related problems, but did
    not see the problem I
    >> am
    >> having.
    >>
    >> Anyway, I have done a website template for someone
    and I gave it to him
    >> to
    >> update the contents. However, on his dreamweaver
    Design view, the css
    >> does not
    >> support it at all so it looks all messy. Though when
    he preview it on IE,
    >> this
    >> is all fine. I have made templates and css files
    with dreamweaver and I
    >> can
    >> view everything fine. He seems to have the same
    version of DW (MX 2004)
    >> so I am
    >> not sure how this happens. We were looking in
    everything (including goofy
    >> css
    >> as someone says on this forum), but have no luck so
    far. Here is my link
    >> and I
    >> pasted my css here.
    >>
    >>
    http://www.norithefish.com/index2.html
    >>
    >> Many thanks for this.
    >> Noriko
    >>
    >> /***********************************************/
    >> /* HTML tag styles */
    >> /***********************************************/
    >>
    >> body
    >> {background: #cccccc; font-family: Verdana, Arial,
    Helvetica, sans-serif;
    >> font-size: small; color: #000000; font-weight:
    normal}
    >>
    >> a { color: #333333; text-decoration: none }
    >>
    >> a:active { color: #666666; text-decoration: none }
    >>
    >> a:hover { color: #CC3300; text-decoration: underline
    >>
    >> .bodytext { font-size: small; color: #000000;
    font-weight: normal}
    >>
    >> .smalltext { font-size: x-small; color: #000000;
    font-weight: normal}
    >>
    >> .smalltextw { font-size: x-small; color: #ffffff;
    font-weight: normal}
    >>
    >> .title{ font-size: 1.5em; font-weight: bold; color:
    #CC3300}
    >>
    >> .wbracket{ font-size: small; font-weight: normal;
    color: #ffffff}
    >>
    >> .smalltitle { font-size: 1em; font-weight: normal;
    color: #666666}
    >>
    >> .sub { font-size: small; font-weight: bold; color:
    #ffffff }
    >>
    >> .foot { font-size: x-small; font-weight: normal;
    color: #000000}
    >>
    >>
    >> h1 {
    >> font-family: Verdana, Arial, Helvetica, sans-serif;
    >> font-size: 1.5em;
    >> color: #cc3300
    >> }
    >> h2 {
    >> font-family: Verdana, Arial, Helvetica, sans-serif;
    >> font-size: 1.15em;
    >> color: #cc3300
    >> }
    >> h3 {
    >> font-family: Verdana, Arial, Helvetica, sans-serif;
    >> font-size: 1em;
    >> color: #666666
    >> }
    >>
    >> ul{
    >> list-style-type: square;
    >> }
    >>
    >> ul ul{
    >> list-style-type: disc;
    >> }
    >>
    >> ul ul ul{
    >> list-style-type: none;
    >> }
    >>
    >>
    >> /***********************************************/
    >> /* Layout Divs */
    >> /***********************************************/
    >>
    >> #pageNav{
    >>
    >> float: left;
    >> width:21.3%;
    >>
    >> top:10px;
    >> padding-left: 0px;
    >> border-bottom: 1px solid #cccccc;
    >> border-right: 1px solid #cccccc;
    >> }
    >>
    >> #content{
    >> width:75%;
    >> float: left;
    >> padding: 0px 0px 0px 0px;
    >>
    >> margin: 0px 0px 1px 20px;
    >>
    >> }
    >>
    >>
    >> /***********************************************/
    >> /* Component Divs */
    >> /***********************************************/
    >> #siteName{
    >> margin: 0px;
    >> padding: 16px 0px 8px 0px;
    >> color: #ffffff;
    >> font-weight: normal;
    >> }
    >>
    >>
    >> /************** feature styles *****************/
    >>
    >> .feature{
    >> padding: 0px 0px 0px 0px;
    >> font-size: 100%;
    >>
    >>
    >> }
    >>
    >>
    >>
    >> /************* #siteInfo styles ***************/
    >>
    >> #siteInfo{
    >> clear: both;
    >>
    >> font-size: 100%;
    >> background-color: #999999;
    >> padding: 0px 0px 0px 0px;
    >> border-top: 1px solid #666666;
    >> }
    >>
    >> /************* #smalltitle styles ***************/
    >>
    >> #smalltitle{
    >> clear: both;
    >>
    >> background-color: #ffffff;
    >> font-size: 100%;
    >> padding: 0px 0px 0px 0px;
    >> border-top: 1px solid #CC3300;
    >> border-bottom: 1px solid #CC3300;
    >>
    >> }
    >>
    >>
    >>
    >> /*********** #sectionLinks styles ***********/
    >>
    >> #sectionLinks{
    >> position: relative;
    >> width: 150px;
    >> margin: 0px;
    >> padding: 0px;
    >> border-bottom: 1px solid #cccccc;
    >> font-size: 90%;
    >>
    >> }
    >>
    >>
    >>
    >> #sectionLinks a:link{
    >> font-size: 1.15em;
    >> padding: 2px 0px 5px 10px;
    >> border-top: 1px solid #cccccc;
    >> width: 100%;
    >>
    >> width: auto;
    >> }
    >>
    >> #sectionLinks a:visited{
    >> font-size: 1.15em;
    >> border-top: 1px solid #cccccc;
    >> padding: 2px 0px 5px 10px;
    >> }
    >>
    >> #sectionLinks a:hover{
    >> font-size: 1.15em;
    >> border-top: 1px solid #cc3300;
    >> background-color: #dddddd;
    >> padding: 2px 0px 5px 10px;
    >> }
    >>
    >>
    >>
    >>
    >> /*********** .frame styles ***********/
    >> .frame {
    >> width: 700px;
    >> left: 50%;
    >> padding-top: 0px;
    >>
    >> margin-left: -350px;
    >> margin-top: 0px;
    >> position: absolute;
    >> visibility: visible;
    >>
    >> border-top: 1px solid #999999;
    >> border-bottom: 1px solid #999999;
    >> border-right: 1px solid #999999;
    >> border-left: 1px solid #999999;
    >> background-color: #ffffff;
    >> }
    >> .bg {
    >> height: 1px;
    >>
    >> background-color: #cccccc;
    >> width: 100%;
    >> }
    >>
    >> /*********** #pageNav link styles ***********/
    >>
    >> #pageNav ul a:link, #pageNav ul a:visited {display:
    block;}
    >> #pageNav ul {list-style: none; margin: 0; padding:
    0;}
    >>
    >> /* hack to fix IE/Win's broken rendering of
    block-level anchors in lists
    >> */
    >> #pageNav li {border-bottom: 1px solid #EEE;}
    >>
    >> /* fix for browsers that don't need the hack */
    >> html>body #pageNav li {border-bottom: none;}
    >>
    >> /********************* end **********************/
    >>
    >>
    >>
    >>
    >
    >

  • How do i get two spry tabbed panels to render properly in design view?

    I have inserted two spry tabbed panels into a simple web page.  The second panel appears off to the side of my design view window.  When i preview it in a browser it comes out fine but i can't seem to get the design view the same.  If i insert new paragraphs the tabbed panels look okay in the design view, but when viewing in the browser theres waaay to much space between them.  Any suggestions?

    Without seeing your page, not much to suggest other than making sure your code is valid.  DW is sensitive to coding errors that some browsers will overlook.
    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

  • CSS style not rendering in design view

    I have style="max-width:600px" in a image but it wont show in design view on Dreamweaver CS4

    The parent file MUST be named with .shtml or .shtm as an extension.  It's that extension that tips the server off that the file contains server directives and that it should be parsed to find them (normally, fetched files are not parsed by the server).  Using these filename extensions will not affect the XHTML strict validation of the file (by the way, is there a reason for sticking with XHTML?).
    It is not necessary to have a testing server defined to see proper HTML includes rendered in Design view.  I believe that by renaming your file with the correct extension you will see this include expressed in Design view. It is a little unclear to me whether the correct syntax for a virtual include is to use the root slash or to omit it.  For example, Wikipedia says -
    The file parameter defines the included file as relative to the document path; the virtual parameter defines the included file as relative to the document root.
    Then later it says -
    The file parameter defines the included file as relative to the document path; the virtual parameter defines the included file as relative to the document root.
    There is, in fact, a big difference between these two statements!  From a personal point of view, I don't use HTML includes at all (always use PHP includes which are written differently).  But I think you can use the file include as I have shown safely - that's assuming that the two files are at the same level.

  • Design View Renders YUI CSS Incorrectly

    I am evaluating Dreamweaver CS3 and find that opening a web
    page using YUI reset-fonts-grids CSS does not render correctly
    within design view. I'm rather surprised by this since improved CSS
    support is supposed to be a major feature of this version.
    Am I missing something? Or does rendering CSS styled pages
    remain a problem with Dreamweaver?

    SumBodyElze wrote:
    >> And interestingly enough, neither do the browsers.
    So you will always need to
    > test your
    > > pages in the browsers that matter to your end
    users.
    >
    > True. But the whole point of using YUI's CSS is to
    minimize the discrepancies
    > from browser to browser.
    Remember that that CSS is optimized for display in browsers,
    not within development tools. Dreamweaver won't respond to the
    hacks (see below) the same way a browser will.
    > Anyway, here's the actual page:
    >
    http://www.eugenebarnes.com/dw_cs3_test/index.php
    >
    > And here's a screen capture of the same page from
    Dreamweaver CS3:
    >
    http://www.eugenebarnes.com/dw_cs3_test/DW_CS3_screen.gif
    >
    > As you can see, Dreamweaver fails to stretch the inner
    DIVs to their full
    > width in display view. It doesn't even come close.
    There no way I'm going to go through all the compressed
    mashed up code for the CSS that you have attached to your document
    to see if there are any issues with some specific CSS in there.
    A casual glance at the CSS code *seems* to indicate that the
    code does include some CSS hacks to accomplish what it does for
    browsers. Because DW isn't a browser, it won't have the same CSS
    parsing issues as a browser has (not to say that it won't have any
    issues). It will react differently than browsers will to the hack
    code, and potentially to "regular" code as well. Once you throw a
    hack into the mix, you're really not working in a realm that
    Dreamweaver will be able to accurately represent the hacks.
    You might be able to work around some of the issues by
    creating a new CSS file and attach it as a design time style sheet
    ( Text -> CSS Styles -> Design time) , and set the width of
    the wrapper for the columns to something that displays what you
    want it to, perhaps it's 100% or perhaps its a fixed width. That
    may allow Dreamweaver to display the content similar to the way
    that your browser does.
    HTH
    Danilo Celic
    | Extending Knowledge Daily :
    http://CommunityMX.com/
    | Adobe Community Expert

  • Design view in DreamWeaver CS3 disabled for CSS & Java

    I currently use Adobe Dreamweaver CS3, and only some files have the option to view them in code AND in design view. This works for most files (HTML, PHP, etc). However, anytime I create a new CSS or Java file, the design view is disabled:
    I have already tried the two other solutions I've found in this forum.
    First I tried Preferences > File Types / Editors, and I deleted all of the file types in the "Open in Code View" menu (pictured below).
    I restarted DW, and it didn't work.
    Then I tried several steps to re-create the Configuration folder (which it did, but the problem remained) listed here: http://kb2.adobe.com/cps/401/kb401118.html.
    Still nothing. HTML, PHP, ASP and all other files have the Design View and Split View available, but CSS and Java do not. I would really like to use DW to start editing CSS, but do not know it well enough to write in code and therefore could really use that handy Design View so I can learn as I tweak it.
    Any help much appreciated - thanks!

    HTML, PHP, ASP and all other files have the Design View and Split View available, but CSS and Java do not.
    That's correct. That's as it should be.
    A CSS file contains a bunch of text only CSS rules. Javascript is text-only script. There's no layout to see for CSS and JS files in Design and Split View so they're disabled.
    Files with layout e.g. .htm, .php have Design View because they're web pages with a layout which can be viewed.
    I would really like to use DW to start editing CSS, but do not know it well enough to write in code and therefore could really use that handy Design View so I can learn as I tweak it.
    Open any .htm or .php (or other) web page and its associated CSS file.
    Then tweak the CSS either via Code View in the CSS file, or using the DW CSS Editor when viewing the .htm/.php file, and see the formatting changes applied in Design View in the .htm (or .php) file.
    Do not rely on DW's Design View as an absolute reference for pixel perfect accuracy. It will always be an approximation only to assist visually oriented web designers while editing.
    Always test all CSS rules and edits in a range of browsers. Browser support for CSS rules and effects varies. Not all browsers support everything on offer in CSS1, CSS2 and CSS3.

  • Design View to use CSS included in header

    In all views except the "Design" view, when you look at a page anything that's included in a CSS file imported from the assets/ folder will show HTML styled with the CSS.
    However, in the Design view it doesn't use that linked CSS file. Any hand-coded CSS is used for HTML elements, (e.g. if I use the <style>..</style> tag), but not stuff in the imported CSS file.
    Is there any way to fix this? This editor is too small for more than a couple lines of CSS -- and if it's an external file we can just edit this file in Edge code.
    The workaround is to copy and paste your whole CSS file into this field.

    Interesting.  I think you're right about the quirks mode.  Once I specify the doctype at the top, it looks consistent everywhere...with almost no padding.  That kind of sucks actually.
    New Code:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <title>Untitled Document</title>
    </head>
    <body>
    <ol style="padding-left: 10px;">
        <li>stuff</li>
        <li>things</li>
    </ol>
    </body>
    </html>
    I guess this site has actually had CSS that probably is doing the opposite of what they wanted for years now.  Thanks.  Good catch on quirks mode.  I've been in the bad habit of never using the doctype declarations in my HTML documents and you've opened my eyes to start actually doing this now.  I can now open, reopen, 100 times and I always get the same result.

  • Is there anyway to lock CSS rules?  What's happening in design view?

    Hi,
    I have no idea what I've  done, but I've accidentally  deleted some CSS rules.  Now my design view shows almost a random pattern, yet most things seem to still be working when I view it in a browser.
    So,
    Is there a way to lock CSS rules so that you don't accidentally loose them?  Is there a way to toggle them on and off?  Why does my design view suddenly look all whacked out?
    The jpg shows my design view and here is the link to the page.
    http://test.taffyproductions.com/reservations.htm

    You have an id set on one of the divs, but there is no rule for that ID selector:
    <div id="sidebar2-1"><img src="_images/sidebar2.jpg" alt="sidebar2" width="180" height="479" /></div>
    Change the id to sidebar2  and see what happens.  The page should fall back into place correctly.
    There is no way to 'lock' in styles, you just need to be careful on  editing the style rules as you go 
    You could always keep a backup copy of a stylesheet that works correctly and if you then want to play around with the rules, do so, but knowing that you have a backup copy if you need it.
    I'd also take a look at the naming convention you use for file names.  I'd not start a file name or folder with and underscore... some browsers may choke.  always better off starting a name with a letter, no characters, or numerals etc.,to be on the safe side.
    Nadia
    Adobe Community Expert : Dreamweaver
    Unique CSS Templates | Tutorials | SEO Articles
    http://www.DreamweaverResources.com
    Web Design & Development
    http://www.perrelink.com.au
    http://twitter.com/nadiap

  • Why cant DW CS5.5 show html5's new elements in the wysiwyg design view?

    Why cant DW CS5.5 show html5's new elements in the wysiwyg design view?
    I created a <section> and an <aside> in code view, and styled those elements in my CSS, but it doesnt show anything in design view!
    why not?
    Its annoying.
    CS5.5 is Adobe's spring 2011 release.
    Why is it not up to speed??
    Isnt html5 very 2009-2010ish?
    Is there an add-on i can install?
    thanks.

    Well we are all "getting up to speed" with HTML5 because, as it stands, it is still not a standard.
    As to styling in CS4 vs CS5.5, Dreamweaver is an engine that assists in making good HTML code. It's agnostic. If you don't close your tags properly in CS 5.5 and then open the same document in CS4, it will notice that you did not close your tags properly.
    Adobe makes plugins that will allow CS4 to do code hinting properly with HTML5 selectors and CSS3, assuming the document is peroperly defined as an HTML5 document.
    Here is the beginning of one of my most recent HTML5 documents:
    <!DOCTYPE HTML>
    <html>
    <head>
    <meta charset="UTF-8">
    <title>Page Title Goes Here</title>
    <link href="css/normal.css" rel="stylesheet" type="text/css" media="all">
    <link href="css/navigation.css" rel="stylesheet" type="text/css" media="all">
    <!-- include CSS before the Shiv -->
    <!--[if lt IE 9]>
    <script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
    <![endif]-->
    This works.

  • Site no longer previewing in design view

    Hello,
    The site I need help with is a classic asp site. I am using Dreamweaver CS5.5 and am working in Windows 7 Professional.
    For over a year I have been opening files directly from two separate servers (one is testing, the other is live) and the files previewed fine in design view. One day design view stopped working for asp files on both servers and I do not know what caused this. HTML files still preview fine.
    On the live server, design view is not recognizing the included header, any of the css, or the images when I open .asp files. When I paste the include into the main document I can get the css to work by removing the initial '/' character from the path leading me to believe this is a pathing issue. I do not want to change my pathing in the files as the site is rendering properly in the browser and there is not a inital '/' character in the includes original path to remove anyway.
    When I open a .asp file from the test sever, the included file is showing in design view but again I have to change the pathing to the css in order for it to render properly in design view. It is rendering properly in the browser.
    The loss of design view is making my styleing very challenging. I think I need to tell dreamweaver where the root of the testing and live server are. I'm not sure is this is the solution and if it is I am not sure how to implement it. Any help would be greatly appreciated. Thank you.
    Paul

    Thanks Nancy...   Here is what I found. Maybe you (or someone could shed some light on this for me).
    Here is what is placed in all of my documents: 
    <!--#include virtual="/includes/topNav/topNav_housing.asp"----------->
    The home page that displayed properly in Dreamweaver looked like this:
    <!--#include virtual="/includes/topNav/topNav_home.asp"-->
    Removing all but two of the dashes as the end of the code snippet fixed the problem and the Header started to disply in Design view.   I am not a programmer, and my HTML/CSS knowledge is self taught, but this code has been in place from a previous designer for years.  Does it make a difference?  What could have changed?   I have thousands of these pieces in my site, I guess I need to fix them all.....

  • Design view in DW MX 2004 v7.0.1

    How can I set up the design view to show me what the page
    actually looks like? I'm going back to doing tabled webpages
    because it obviously can't handle CSS div tags, but the design view
    shows my tables (rows/columns) with dashed lines, a bunch of green
    arrows and pixel widths, etc. All I want to see is what the page
    looks like. Am I screwed and have to alt+tab over to an IE window
    to view my changes? Note: I'm working on a prototype for a
    website-these are just going to be click-thru screens (no real
    data, no 508 compliance, IE only, internal application).

    > How can I set up the design view to show me what the
    page actually looks
    > like?
    Actually looks like? In which browser? In which version? In
    short, there
    is no way to do this. Preview in the desired browsers to see
    what it
    actually looks like. And code the page so that it validates
    to get the most
    reliable cross-browser rendering - but be aware, DMX2004 is
    not the best at
    rendering CSS layouts.
    > it obviously can't handle CSS div tags
    Huh?
    > tables (rows/columns) with dashed lines,
    > a bunch of green arrows and pixel widths, etc.
    VIEW | Hide Visual Aids
    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
    ==================
    "rx7dave" <[email protected]> wrote in
    message
    news:f2adj7$q4h$[email protected]..
    > How can I set up the design view to show me what the
    page actually looks
    > like?
    > I'm going back to doing tabled webpages because it
    obviously can't handle
    > CSS
    > div tags, but the design view shows my tables
    (rows/columns) with dashed
    > lines,
    > a bunch of green arrows and pixel widths, etc. All I
    want to see is what
    > the
    > page looks like. Am I screwed and have to alt+tab over
    to an IE window to
    > view
    > my changes? Note: I'm working on a prototype for a
    website-these are just
    > going
    > to be click-thru screens (no real data, no 508
    compliance, IE only,
    > internal
    > application).
    >

  • Design view goes blank [CS3]

    I usually work with split code + design view
    When working with certain files and make a change in code
    view(or in a linked .css), and then click in Design view, the
    Design view goes totally or partially blank. Either nothing appears
    at all, or the content appears up to some point, and the rest up to
    the end is blank.
    Once this happens, there is absolutely no way to make the
    'hidden' content visible. Tried to switch to another file, to
    select code in code view, to edit in code view or even in design
    view - no go. I have to close / open the file, and then it appears
    normally. But indeed I can't do this every minite, is there some
    solution known?
    There is no stuff with visibility set to hidden or alike, if
    the content is displayed - it's displayed correctly. Also looks OK
    in all major browsers.
    Thanks

    This often happens when you have added such garbage code that
    DW cannot
    figure out what to do with it. For example, adding a
    <body> or </body> tag
    in the middle of a page can do such things. Might that be
    what's happening
    for you?
    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
    ==================
    "harpo_" <[email protected]> wrote in
    message
    news:f2nq7t$dse$[email protected]..
    >I usually work with split code + design view
    > When working with certain files and make a change in
    code view(or in a
    > linked
    > .css), and then click in Design view, the Design view
    goes totally or
    > partially
    > blank. Either nothing appears at all, or the content
    appears up to some
    > point,
    > and the rest up to the end is blank.
    > Once this happens, there is absolutely no way to make
    the 'hidden' content
    > visible. Tried to switch to another file, to select code
    in code view, to
    > edit
    > in code view or even in design view - no go. I have to
    close / open the
    > file,
    > and then it appears normally. But indeed I can't do this
    every minite, is
    > there
    > some solution known?
    >
    > There is no stuff with visibility set to hidden or
    alike, if the content
    > is
    > displayed - it's displayed correctly. Also looks OK in
    all major browsers.
    >
    > Thanks
    >

  • Design view of jspx not rendering : Error exercising tag : afh:head

    I'm using JDeveloper 10.1.3.4 and I have an intermittent problem where by the jspx does not render correctly in design view - it just shows a whole load of nested boxes.
    By following a suggestion from another website I turned on "Design time messages in log" in jdeveloper JSP visual editor preferences.
    The error messages being sent to the log window are :
    Error exercising tag : afh:head
    java.lang.NullPointerException
         at oracle.adfinternal.view.faces.renderkit.AdfRenderingContext.getTranslatedString(AdfRenderingContext.java:70)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.jsLibs.GlobalVariablesScriptlet.outputScriptletContent(GlobalVariablesScriptlet.java:49)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.jsLibs.Scriptlet.outputScriptletImpl(Scriptlet.java:111)
    Error exercising tag : af:forEach
    javax.servlet.jsp.JspTagException: 'begin' and 'end' should be specified if 'items' is not specified
         at oracle.adfinternal.view.faces.taglib.ForEachTag._validateAttributes(ForEachTag.java:320)
         at oracle.adfinternal.view.faces.taglib.ForEachTag.doStartTag(ForEachTag.java:93)
    Error exercising tag : afh:body
    java.lang.NullPointerException
         at oracle.adfinternal.view.faces.renderkit.core.CoreAdfRenderingContext.getStyleClass(CoreAdfRenderingContext.java:211)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.XhtmlRenderer.renderStyleClass(XhtmlRenderer.java:338)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.PanelPartialRootRenderer._renderLibraryDownloadElement(PanelPartialRootRenderer.java:480)
         at oracle.adfinternal.view.faces.renderkit.core.xhtml.PanelPartialRootRenderer.renderPPRSupport(PanelPartialRootRenderer.java:340)
    How can I fix this ?
    Cheers,
    Brent

    Hi Didier,
    Sorry, intermittent problem is not very descriptive ! What I actually meant is that some of my applications have the problem while others dont. Once the problem exists, it always does regardless of restarting JDeveloper.
    Starting JDeveloper using the console provided similar error message to outputting the JSP visual editor to the log file :
    SEVERE: Element End name:head does not match start name:script
    04-Dec-2009 17:28:38 oracle.adfinternal.view.faces.io.HtmlResponseWriter endElem
    ent
    SEVERE: Element End name:html does not match start name:div
    Reading other posts, problems seemed to stem from errors within the faces-config or web.xml files so I compared them between apps displaying pages correctly and ones that weren't. I found a difference in the filter-mapping section of the web.xml. Changing the entries to match the applications that displayed correctly has worked !!
    The entries for the apps that didn't display correctly :
        <filter-mapping>
            <filter-name>adfFaces</filter-name>
            <servlet-name>Faces Servlet</servlet-name>
            <dispatcher>FORWARD</dispatcher>
            <dispatcher>REQUEST</dispatcher>
        </filter-mapping>
        <filter-mapping>
            <filter-name>adfBindings</filter-name>
            <url-pattern>*.jsp</url-pattern>
        </filter-mapping>
        <filter-mapping>
            <filter-name>adfBindings</filter-name>
            <url-pattern>*.jspx</url-pattern>
        </filter-mapping> 
      <filter-mapping>
        <filter-name>adfBindings</filter-name>
        <servlet-name>ordDeliverMedia</servlet-name>
      </filter-mapping>
      <filter-mapping>
        <filter-name>jhsAuthenticationFilter</filter-name>
        <url-pattern>*.jsp</url-pattern>
      </filter-mapping>
      <filter-mapping>
        <filter-name>jhsAuthenticationFilter</filter-name>
        <url-pattern>*.jspx</url-pattern>
      </filter-mapping>... and the entries for the apps that did display correctly :
        <filter-mapping>
            <filter-name>adfFaces</filter-name>
            <url-pattern>*.jsp</url-pattern>
        </filter-mapping>
        <filter-mapping>
            <filter-name>adfFaces</filter-name>
            <url-pattern>*.jspx</url-pattern>
            <dispatcher>REQUEST</dispatcher>
            <dispatcher>FORWARD</dispatcher>
        </filter-mapping>
        <filter-mapping>
            <filter-name>adfBindings</filter-name>
            <url-pattern>*.jsp</url-pattern>
        </filter-mapping>
        <filter-mapping>
            <filter-name>adfBindings</filter-name>
            <url-pattern>*.jspx</url-pattern>
            <dispatcher>REQUEST</dispatcher>
            <dispatcher>FORWARD</dispatcher>
        </filter-mapping>
        <filter-mapping>
            <filter-name>adfBindings</filter-name>
            <servlet-name>ordDeliverMedia</servlet-name>
        </filter-mapping>
        <filter-mapping>
            <filter-name>jhsAuthenticationFilter</filter-name>
            <url-pattern>*.jsp</url-pattern>
        </filter-mapping>
        <filter-mapping>
            <filter-name>jhsAuthenticationFilter</filter-name>
            <url-pattern>*.jspx</url-pattern>
        </filter-mapping>Somehow the filter-mapping entries for the adfFaces and adfBindings filter got all screwed ? Strange as the application has always worked fine, the only (obvious) problem has been the jspx pages not rendering properly in design view.
    Once updating the web.xml with the correct value for these two entries, the pages are displayed correctly :)
    While I don't like blindly making changes like this to the web.xml - the application still seems to function !
    Cheers,
    Brent

  • Working in Design View on the server

    I was given a bunch of (.tpl) files that are on a server. I have to edit them in Dreamweaver (CS3) but the thing is, in Design View I can't see what the pages actually look like. The reason for that is because the CSS isn't showing in Design View (the page looks unstyled). Is there a way to have the CSS files "work" while I'm using Design View? Thanks.

    AFAIK, DW doesn't support TPL (template) files by default.
    But you can add file extensions to DW.  See below:
    http://kb2.adobe.com/cps/164/tn_16410.html
    Once you have the TPL file open in DW Design View, it should look much like any other HTML page.
    If the TPL doesn't contain any inline styles or is not linked directly to an external CSS file, look at Design Time Stylesheets.
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

Maybe you are looking for

  • How can I switch my accounts/files/data from my Macbook to iMac

    I have a 3 year old Macbook running Leopard, and my wife has a brand new iMac running Snow. I have a user account on her comp (not admin), and I want to copy all of my files/user info from my laptop to her computer. Is this possible? How do I approac

  • I lost all songs on my Ipod Touch

    I don't sync my IPod Touch because I have 120 GB of music in ITunes.  So, I manually drag and drop from my library to my IPod.  I did it once, then, for some reason, they all disappeared.  For some other odd reason, the playlist was still left...just

  • FILE_GET_NAME and FILE

    Hi Experts,       Can any one explain the use of Function moudule File_Get_name and the use of Transaction Code FILE.

  • Minimum settings required to implement the https in portal

    Hi, Currently SAP Portal connected with SAP R/3 and ADS server and all are running on http protocol. Current requirement is to implement the Https in portal only. So can you please write me what is minimum settings are required to implement the https

  • Runtime.exec(" find . -name *.txt -exec rm {} \; ") don't work why?

    Hi, I have to exec a unix command like " find . -name *.txt -exec rm {} \; " in a java program, but it don't work fine because of option -exec. The source is : String line="",lineErr="",comando=""; try comando=" find . -name *.txt -exec rm {} \; "; p