Design View is un-usable

I am using the new Flashbuilder 4 on a Macbook Pro running Parallels for using Windows XPpro. I installed the trial version of Flashbuilder 4 and when I go to the "Design View" my display is whitted out. By this I mean the entire display is white with no icons, no canvas, no toolbars showing. If I roll my cursor over some of the icons they will appear, however, this is not true for all the icons and menus. If I use "Source View" then the application seems to run fine. While I had a thread discussion at Flashbuilder 4  brings machine to screeching HALT! I opened this discussion as it addresses a completely new item as I realized the topic and initial details related to problems/solutions which I "thought" were right, but not. This topic addresses a more true series of events surrounding my problem.
thank you
Alex

I was reading some Forum posts at http://forums.adobe.com/thread/604122 and found these entries:
Peter deHaan (Adobe) said in a forum topic about "Flash Builder 4 Extremely Slow under Windows 7 + Java" ...http://forums.adobe.com/people/Peter%20deHaan%20(Adobe)
No, I would not consider that big. But if code hinting is slow also,  that may be more of an OS/Builder thing and not really a Flex SDK issue.  I have a Windows 7 and Windows XP laptop at work and run Windows 7  Ultimate at home and havent seen any performance problems (although I'm  not sure which are running 32 bit vs 64 bit OSes actually).
while Jason San Jose said this about the JVM ...
Are you using a 64-bit JVM? It  sounds like you're running Flash Builder Plug-in, so try this:
1) Close  Eclipse
2) Open the eclipse.ini file where your eclipse.exe is  located
3) Add a new line after "-vmargs" and on that line type  "-d32"
4) Restart Eclipse
A 32-bit JRE is required http://www.adobe.com/products/flex/systemreqs/.  "-d32" will force your JVM into a 32-bit mode.
You're  likely seeing Design view crash because Flash Player support for 64-bit http://kb2.adobe.com/cps/000/6b3af6c9.html.
Alternatively,  you can install a 32-bit JVM and assign that to JAVA_HOME.
Would either of these recommendations be a solution to my "Design View" rendering problem?
Alex

Similar Messages

  • Design View not rendering content of pages

    I am the webmaster and lead developer for a state university. We have developed a responsive Dreamweaver template for our mostly non-coding users (admin assistants usually are assigned web tasks for some reason). You can see our site here http://www.wwu.edu/webtech . When we bring up pages in Design View, they cannot be edited; none of the content is visible. Live view is pretty good, but it's difficult for non-coders to edit in this window. For instance, in Design view they can just select Enter after a block of text to start a new <p>; In Live View you can modify an existing paragraph as if you were in Design View, but you cannot add elements without using the Insert tool. My non code users have no idea what the Insert menu is talking about. So my questions are:
    1. First - has anyone else hit situations where Design View did not work? Here is what it looks like for the site mentioned above:
    2. Any idea why design view cannot handle this page? It's a standard responsive site with media queries... I've tried stripping out complexity but cannot get it to work. It is valid HTML and passes tests.
    3. Am I using the wrong product? Can Muse handle Dreamweaver templates?

    Nancy O, osgood_, Fritz, thank you for your thoughts.
    Dreamweaver has been a wonderful tool for non-coders for many years. We developed templates for the groups, then all they had to do was put the content into the correct areas through the power of the Dreamweaver template. That is no longer possible it seems with the more complex, responsive templates. And yes, Osgood_ , it does appear that some pages will be rendered fine in Dreamweaver. Our older templates such as represented by this site: http://www.wwu.edu/bservices IS viewable and editable in Dreamweaver Design view. Those users are quite happy. However our newest responsive Dreamweaver templated sites such as http://www.wwu.edu/webtech and http://www.wuw.edu/registrar2 are not.
    What I'd really love is for an adobe engineer to sit down and look at our templates and let me know if there is anything I could do to make these templates usable in Design View.
    Our other alternative is to move away from static HTML and Dreamweaver and go entirely to WordPress and Drupal. I will miss Dreamweaver when this happens! I had hoped there was a place for those who did not want the complication of a Wordpress site...

  • DESIGN VIEW in blocks, dashed lines

    I'm using DW CS5.5.  Up until today, design view was working.  Now I'm getting everything in blocks with dashed lines surrounding it.  I have no idea how this happened or how to get it to go back to a usable design view.  Live View is working, but I really need Design View to also work.
    I've tried finding an answer in the Adobe manuals, but that was fruitless.  No "troubleshooting".  DW CS5.5 seems to be a very glitchy application -- I've searched the web and there seems to be a lot of people out there who are having problems with DW that just pop-up out of no where and then fixing them takes hours and lots of researach.  I've tried posting on this forum before, but never got a reply and there's no Adobe support that seems to be available where someone can ask a question.  So, I guess this is it.  Can anyone out there tell me why they think this happened all of a sudden and on it's own?  Thank you.

    Hi Nancy,
    Well, you know that old saying, "can't see the forest for the trees".  I didn't reboot, but I did shut down DW and restarted it, and to my great surprise, Design View was back in WYSIWYG.  I hadn't really been doing anything before this happened, just had switched to Live View and then back to Design View.  My computer is 1.5 months old and it's a dual processor, top of the line Toshiba, so I don't think that was the issue.  Who knows with this software, I'm finding this version of DW CS5.5 to be very glitchy.
    If you would, could you please look at my other post I just put out there regarding why my Footer won't clear the buttom of the above div's.  I've tried everything, but nothing is working except giving it a Position:Absolute.  I want to give it a Position:relative and then just have it clear the div's above it.  The content background div also won't go all the way down.  I think I must have SOMETHING in there that's causing these div's to stop, but I've looked and looked and used the "comments" code to disable and then turn back on one by one and still can't find a solution.  It's very frustrating, especially since it's also now affecting my template since I made everything editable for my new pages I need to prepare.
    Btw, nice to hear from someone, I've posted before and never seem to get an answer or even response.  Trying to contact Adobe seems to be of little use. Again, thank you.

  • Flash Builder 4 - design view - states basedOn + design area widget

    Hello,
    Since i updated my project from Flex 3 to Flash Builder (4), i have very annoying issues in the design area.
    The one in Flex 3 was quite usefull, but the new version is not easy, and straight forward usable.
    Here are the 3 issues:
    - when i have states designed from another one, i use the basedOn mxml attribute, which was used in Flex 3  and still exist in SDK 4 states system.
    But the designer view in Flash Builder don't take those basedOn properties in account!
    What can i do? and is it a known bug?
    -  When i have at least one precific state, i must define a defautl state, in the new SDK. Ok, but in design view, i cant add a new component without making the change only for one state. I can only make the change for the default state, but it will not be taken in account for all the other states, like i can do in Flex 3.
    What i want to be able to do this: making changes in design view without selecting ANY state.
    Is it possible? How can i do?
    - In flex 3, there were a design area widget to select the resolution used for the preview design.
    It was very usefull when the application has very dynamic width and height.
    In Flash Builder, this widget has been removed.
    Why has it been removed? and how can i preview my mxml views wihtout changing width and height values?
    Thanks.
    Seb

    The update has been improved in every other areas, so it is not that much important.
    I just hope that the new release will fix that (as it has been answered to my post).
    The only thing i don't like in new releases of FB is that when the architecture of SDK is aimed to seperate the work between design and code, they focused only on catalyst to create the tools to manipulate design, and they forgot to keep an easy way to do design app directly in FB (with the design view and the style properties of MXML in FB3). But i'm confident that they will give such a tool soon.
    But for now, if you don't like the restriction of the new release, you can continue to work with Flex 3 for 0$! And even in Flex 4, you can create MX components for which the design view will work as before. The fact that tools can manage a mix between MX and Spark components is a great thing. It is up to you to choose which you need which its own advantages and drawbacks.
    Xcode is real pain to use with outdated ergonomy. It is only usefull to code in Objective C which is another real pain to do.
    XCode can be cheapper because all Apple products are quite expansive, so the software to create softwares for them can be much more cheapper.
    And Apple get a good revenue share from AppStore, so again they can give a cheap soft to create apps. You also have to pay 100$ to be able to send app to appstore, in ly opinion the good price for XCode should be 0$, not even 80$!
    Flash builder 4 is very stable, but if you don't like it, you can choose another tool. Main competitor has no designer at all!

  • Third Party Component Support in Design View

    in this article:"
    http://flexwiki.adobe.com/confluence/display/ADOBE/Flex+Builder+3+Planning"
    the follow is shown:
    Third Party Component Support in Design View
    Planned milestone: M3
    Flex Builder should have better support for third-party
    components in design view. Also, the components view and the
    properties view should be just as good for 3rd party components as
    it is for Adobe Flex components like charting and advanced data
    grid controls.
    * The component author should be able to specify the
    category for the Components panel.
    * The component author should be able to control the
    Standard View property sheet including the Common and Style
    categories
    * A component developer should be able to deliver a single
    component in a SWC that contains all appropriate information
    * The component author should be able to include Design view
    extension code to specify Design View surface behavior
    * The component author should be able to specify the default
    code that gets inserted when a component is dropped on the stage
    I wonder how to specify the category for my components, is
    that some compile options or some configure file?
    thx

    /bump
    Noone any information about that topic? This would be a great
    usability enhancement...
    Regards

  • Command Button colors corrupt after switching back and forth from design view.

    I would say my experience level with Access is "getting there."
    I therefore don't thing I'm making a newbish mistake.
    Has anyone else noticed this?  As it's bugging me quite badly.
    1.  A command button has had it's color formatted (pressed, hover, etc. nothing fancy)
    2.  It works fine.
    3.  In my navigation form, if I switch to design view, then select a given sub-form... like "customers" - and switch back out of design view, to form view - then without fail, all customized command buttons within that sub forms' color will 'corrupt'
    ie, change.
    4. Closing and reopening the navigation form (ie, my main menu) restores it, but the same thing will happen should I go back to design view for the sub form.
    5.  Finally - this behaviour does not happen when switching back and forth between views on the original form that isn't a sub form in the navigation form.  (Ie,. the main 'customers' form). 
    Can any clever folk give me a solution? :(
    Thanks,  
    Eric Rowlands
    EDIT - My apologies, I am using Access 2013 for a desktop database.

    1) We will need to understand whether the issue is seen on any sample database.
    2) IS this seen only on your system, we would need to check on other system also
    3) If the issue is seen in all system & issue is not seen in the sample database then this could be database specific issue
    4) As per my understanding the issue is consistent, we would need to find what is the VBA code or which code is used while designing this form.
    5) We would need to see if the issue is seen only on that particular navigation form?
    6) Is the button gets corrupt I mean to say non-usable once it get discolored ?
    7) What is your end goal just in case if you are able to work on your database i.e. when working on the navigation form without going in design view is issue still seen there ?
    8) Since when are you experiencing this issue ?
    9) If possible please provide me the environment details of your system & Access application, whether the issue is seen only in access 2010 can we check in access 2007 or in access 2013.
    I would really appreciate if you can answers the above questions this will really help us to isolate the issue further
    in terms of technical troubleshooting after answering the above question I might come up with another question so that we can do extensive isolating the issue so the if required we can involve the developer also.

  • Dreamweaver CC 2014.1 design view gone - what next?!

    First Adobe deprecates server behaviors, now they are removing design view?!  I am stunned.  Design View is the SOLE reason I use Dreamweaver!  (It's more of a quick code navigator in split view.) Live view has NEVER worked in a practical and usable way, and still seems very quirky at best in this 2014.1 release.
    Adobe, Please don't remove useful tools like this!  What's next; dropping extension support?  Some of us have to make a living using these tools.
    Please help me understand, Adobe.  Why not keep design view as an option?
    ...on to opening CS6 once again so I can continue actually working on projects...

    Design View is still available for normal layouts.  See screenshot.
    If you're not seeing it in the selection list, you're working with Fluid Grid layouts.  But don't panic. You have a couple of options.
    Option #1 -- Trick DW into thinking it's a normal layout by putting an X in your FG Layout CSS file. Do this in Code View, not with Designer Panels.
        Dreamweaver Fluid Grid Properties
        dw-num-cols-mobile:      X 4;
        dw-num-cols-tablet:        8;
        dw-num-cols-desktop:    12;
        dw-gutter-percentage:    25;
    =====================================
    Option #2 -- Drop back to CC 2014.0 (June Release) from these direct links:
    WIN : http://download.adobe.com/pub/adobe/dreamweaver/win/cc/Dreamweaver_14_LS20.exe
    MAC : http://download.adobe.com/pub/adobe/dreamweaver/mac/cc/Dreamweaver_14_LS20.dmg
    Nancy O.

  • Design View suddenly incorrect, Web view looks fine

    I uploaded my site and, after doing so, shut down Dreamweaver. The next day, when I opened it again, my pages in Design View looked completely wrong.  The code seems to be fine and when I preview the pages in Google Chrome they look perfect; all the links work, it's all laid-out correctly. I am semi-new to all this; I need to be able to update the site but don't want to risk uploading over a now usable website and render it unusable.
    If you need screenshots, let me know, but basically, design view is not being reliable (at all) right now.
    Looked at the other post showing same problem but it didn't seem to relate.
    I am using Dreamweaver CS3 with Windows XP Home Edition.

    As Bregent says, you have an unclosed div, hence the problem with the page.   Other couple of errors you may want to fix as well.  Putting the page through a validator always helps to find initial problems  :-)
    Results of putting your page through the validator:
    http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fsugaredmagnolia.com%2F
    HTML Validator - http://validator.w3.org
    CSS Validator - http://jigsaw.w3.org/css-validator/
    If you use the Firefox browser (which you should to check your pages), there is a toolbar add on that you can download, that includes a a validator tool that checks your pages directly from your own computer without having to upload the pages as you work.
    Web Developer Toolbar
    http://chrispederick.com/work/web-developer/
    Nadia
    Adobe® Community Expert : Dreamweaver
    Unique CSS Templates |Tutorials |SEO Articles
    http://www.DreamweaverResources.com
    http://csstemplates.com.au/
    http://twitter.com/nadiap

  • Can not see two fields in Crystal 2008 Developer explorer/designer view

    I am currently developing crystal 2008 reports against the salesforce.com database using version 12.0.0.683 CR Developer Full version. I am using an updated driver that was provided in July or Aug 08 in order to view self referencing fields. The problem is that when I try and report against one of the tables (lead history) I cannot view two of the fields (New Value and Old Value)? I can see these two field (New Value and Old Value) in the database expert as the last two fields in the actual table, but the two fields are missing when I go into the explorer/designer view. In Salesforce, these two fields can not be filtered on, but I can export all the values in this table using Salesforece Apex data loader.

    Please re-post if this is still an issue to the OnDemand Forum or purchase a case and have a dedicated support engineer work with you directly

  • Unable to view php files in Design View?

    Need help! I cannot select design view when working with a PHP document, the DesignView option is disabled?
    My information.
    -          Dreamweaver CS5
    -          Mac OSX 10.6 snow Lepoard
    I have searched online and I also went through the FAQ but couldn’t find anything relating to this particular issue and my Professor at school said that I need to contact Adobe directly as design view should always be available but all that I would see in Design View are the HTML elements within the PHP file.
    The Design View button is disabled, I can not click on it all and so for my class assignments. I have to copy the PHP code into a new HTML document and only then am I able to view the html/php and edit the HTML elements, and then copy and paste it back into the PHP file once I have the html elements/design set up correctly.
    I did a similar “Set up PHP for Mac OS X – MAMP” to the version available here, could I have set this up incorrectly and that is why Design View is disabled?
    Thanks I appreciate your guys expertise and any help!

    Kanjan wrote:
    Need help! I cannot select design view when working with a PHP document, the DesignView option is disabled?
    Go to Dreamweaver > Preferences, and select File Types / Editors from the Category list on the left. Make sure that .php is NOT listed among the filename extensions in "Open in code view".
    Adding a filename extension to that list prevents files from being opened in Design view.

  • What is it about this markup that breaks DW CS3 Design View Editing?

    Folks:
    I'm attaching very simple --and apparently completely valid-- markup that generates the text shown between the markers below:
    ------------start----------------
    yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda yadda badda.
    ------------end----------------
    As you can see by examining the file, it contains only an span enclosing text and spaces, and some following breaks.  This file passes DW validation: no errors or warnings.
    If I open this file in DW CS3 Design View, select and delete the last word, "badda", the entire text --every "yadda"--  is also deleted.  All that text is really gone -- if I immediately save the file and re-open it, there is no text content at all, just the span pair,  spaces, and the trailing breaks.  This is completely repeatable.
    When you edit this file, do you get the same result?
    The attached file is a cut-down, simplified version of a production file that exhibits this issue. (That file also passes validation.)   When I delete single  words,  entire content paragraphs disappear.   So this is not just a point of curiosity.  I need to figure out how to fix the production code and avoid this problem in the future.
    What is it about the attached markup that causes this issue?  I've fooled around with this code quite a bit and the best I can figure out is that DW is confused when both the start- and end- span tags are followed immediately by a line break.  Inserting a space in either place makes the issue go away.   But the production code doesn't have any occurances of this pattern. And, anyway, line-breaks have no significance to html, just for source-code formatting, right?
    Am I missing something incredibly obvious?
    TIA
    hen3ry

    Nancy O:
    Thank you for your response, which gave me  valuable clues to understanding the issues.   (Specifically, it led me to re-read and understand better the nitty-gritty of the HTML4 specs,  section 7, "The global structure of an HTML Document", especially 7.5.1 The BODY element.)
    I believe you are saying --in sum--  that to be reliably edited in DW, each source file must comprise a syntactically correct and complete HTML Document. 
    I am attaching a second file, "badcode2.html", modified substantially as you suggest.  It passes the DW validator, the validator.w3.org test, and the www.totalvalidator.com test.    No errors or warnings. 
    I do this:   Launch DW, open this file, choose Design View if necessary, select the final word of text, "badda", and activate Edit-->Cut (or Delete).   As before, all the other text is deleted as well. This is repeatable. 
    It seems to me this sample code satisfies your general principle.  Could I be misapplying the three validation tests?  Or that passing these tests does not assure the document  is syntactically correct and complete?   Can you recommend other tests? 
    I'd like to add the following two points as a matter of background and a bit of niggling: 
    --I'm aware  that complete HTML pages must contain <html> , <head>,  and <body> tags, although the HTML4 specification seems to say <body> tags are optional.   All my production pages, as served, contain these tags.   My underlying design is a php template with individual content files incorporated by inclusion.   There may be only one set of <html> , <head>,  and <body> in  a  page. The  "outer" template code provides these tags, and individual content files cannot contain a nested set -- so they must be "bare" markup.   Is DW able to support this design, in which "bare markup" files are seemingly unavoidable?    Is there a mechanism analogous to DW Design-Time Style Sheets to provide virtual existence of these tags so "bare markup" files can be successfully edited?  I've looked for such a mechanism but not found one.    Or some completely different method?   
    --You specify the inclusion of <p> or <h1> tags within the  body.    Is there some special significance of <p> or <h1>  with respect to stable editing in DW?  My reading of the HTML4 spec indicates that a single block element is the minimal requirement for body content. Either of these tags qualify, right?   But so does <div>, and that's what I use in my current example.    Am I misunderstanding something? 
    Bottom line,  I'm looking for a pragmatic solution for my problem:   Once in a while, among hundreds of  structurally similar "bare markup" pages I edit in DW without any problem,  I lose data.   If inserting an additional tag into all my content include files eliminates these occasional problems, I'm  willing to do that, as long as:  (1) There is an arguable technical basis for the addition,  (2) the added tag does not  produce anything visible on the served page, and (3) the validators don't flag the extra tag.     
    Suggestions, please! 
    Thanks, 
    hen3ry

  • Can not see the design view nor the java file in CentOS

    Hi all. I've recently installed JSC2 in CentOS. I find this tool really useful. But I have a problem with the design view and the java file view. At the beginning, when I first create a Page1.jsp, I can see the design view and the java view with no problem. I run apps correctly. But after a while, I get a "null pointer exception" error and I am able to see only the jsp view, not the others. I don't even have the option to see the Design and Java views. And the page icon in the project window appears to be darker than a well working page. I'm not really sure what sequence of actions I do to get this error, it just suddenly happens. What I've done so far in JSC2 is to link to pages in the Page Navigation view. It works fine for a while, but after a while I get the error I've described.

    Yes, if I do that It happens the same. I've tried everything. Now I'm using Window$ 2000 and it works properly. Thanks anyway.

  • Images broken in design view on new computer paths leading to old harddrive?

    I recently got a new imac and installed cs5 dreamweaver ( I was using dreamweaver 8 but it no longer works in mountain lion) . I redfined the site all was fine then I must have done something and now suddenly all my images are broken in design view and in brower and live view! The site shows the images online from the server but everything is broken in design view. The directory is a mess as I used way too may subfolders when I first did the site but it's too large to start over. I tried deleting the site from my harddrive all together and creating a new folder for it and just getting the entire site from the server but the images still don't show. I don't want to have to go to every page on the site and fix broken links! I can pull an image into a page by browsing to the folder on my harddrive but they are not appearing anymore on their own. If the images were uploaded originally from another computer and the folder being used now for the site on my harddrive is different that won't break the image paths will it? It all worked fine until a few days ago. What I don't understand is I thought the images wouldn't show if they were only on the server and not on my harddrive but since I just GOT the site from the server, all the images ARE now on my harddrive in the new folder so why still nothing showing? I I tried right clicking the broken images and showing design notes they seem to be lookin for a path to my old computer where the harddrive was named differently than it is now. Is there ANY way to fix this? What about renaming my harddrive to the old name?
    Greatful for any advice but I am very much a newbie so not sure I will be able to do what I need to.
    Mary Ann

    Spaces in folder/filenames are not a good practice.  Space are converted to %20 on the server.  DW's Design View often can't reconcile this.  Best advice is to remove the spaces and use underscores _ or hyphens -
    Rename this:
    http://www.thedqtimes.com/Jane_site/Lake%20Effects/lakeeffectsjdaughters.jpg
    http://www.thedqtimes.com/Becky%20H%20stories/Untitled-1.jpg
    To this:
    http://www.thedqtimes.com/Jane_site/Lake_Effects/lakeeffectsjdaughters.jpg
    http://www.thedqtimes.com/Becky_H_stories/Untitled-1.jpg
    Also, you have a misplaced <head> tag.  It needs to be above the Dynamic drive Javascript code.
    <head>
         <script> </script>
         <style> <style>
    </head>
    Some pages are missing an HTML doc type declaration.  This sends browsers into Quirks Mode.
    Use validation tools to check for other code errors.
    Code Validation Tools
    CSS - http://jigsaw.w3.org/css-validator/
    HTML - http://validator.w3.org/
    Nancy O.

  • Images and styles not showing in Design view on CS3

    Hi all,
    I am playing around with a CSS website template that I downloaded and
    opened in DW-CS3. I am just using this to learn and play around with. It
    came with the style sheet, jpg images etc.
    I just noticed that when in Design view for the index page, that the images
    and styles, menus are not displaying, only the html text is visible in Design view.
    When I preview the site with a browser like IE or FF, it displays fine along with
    any changes I have made.
    Does anyone have any ideas?
    Regards,
    dano

    In DW, View > Style Rendering > Display Styles on?
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists
    http://alt-web.com/
    http://twitter.com/altweb

  • Design view and browser view in DW are different than when I view from local folder

    I'm brand new to Dreamweaver CS5.5 and here is my problem:
    I've made an html page in dreamweaver with a banner, with an additional graphic and some text on top of the banner.  It displays just fine in every browser when I view from the local folder, but when I open DW and view, it displays incorrectly in all three design, live and browser views within DW.  If I make changes to the css file until it views correctly in design view, it no longer displays correctly from the local folder and it still doesn't view correctly in live or browser view within DW.  If what I'm doing isnt going to display accurately in any of the views provided by Dreamweaver as compared to the live server, whats the point in having this software?  I could just keep building webpages in notepad and uploading with CoreFTP.
    Any suggestions?  Is it some setting that I dont know about that I need to change within DW?   Please help.

    align="center" is deprecated (obsolete) code in XHTML & HTML5 doc types.  Instead of styling markup with HTML, you should be using CSS. 
    CSS
    .center {text-align:center}
    HTML
    <p class="center">some centered text here</p>
    With respect to break tags, in XHTML doc types the correct syntax is <br /> not <br>.  However your usage of line breaks is inconsistent with good symantic markup.  Use headings <h1> <h2> <h3> <h4> for important keywords.  Use <p> for descriptive paragraphs.  Use <ul> <li> or <ol> <li> for lists.  Line breaks should be used minimally if ever.
    XHTML doc types require all tags to be lowercase.  Uppercase tags will throw errors.
    Your design is too rigid.  When text size is increased in browsers, your content is unreadable.  See screenshot.
    SOLUTIONS:
    1) DO NOT USE POSITION ABSOLUTE.  You don't need it.  Absolute positioning removes content from the normal document flow resulting in a jumbled mess.  Use default CSS positioning (none) with margins, padding & floats to align elements.
    2) Remove HEIGHT values from all CSS containers.  Height limits a container's capacity to hold more content when needed.  Container height should always be determined by the amount of content it holds; not explicit values.  If required to reveal a background image, for example, use CSS min-height instead of height.
    CSS Box Model
    http://www.w3schools.com/css/css_boxmodel.asp
    CSS Floats
    http://www.w3schools.com/cssref/pr_class_float.asp
    CSS min-height
    http://www.w3schools.com/cssref/pr_dim_min-height.asp
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb
    http://alt-web.blogspot.com/

Maybe you are looking for