Design view issue - CSS and html

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

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

Similar Messages

Can I include both CSS and HTML codes in one Open HTML Editor.

Somehow Cell phones are not properly reading css codes. Is there any way to include both CSS and HTML codes in one Open HTML Editor?

Hammad, their code is fairly mobile friendly. Per my other discussion with you ( http://topliners.eloqua.com/thread/8532 ), Eloqua's code is responsive for the most part. Most of their issues lie with the styling of the email where you will get different fonts and different sized fonts throughout the email and some other minor display issues.
What you are trying to accomplish is extremely difficult to do because you do not have the access to the HTML to better control how the responsive template works which is why the Eloqua templates (and most ESP templates) stick to the more basic side of emails.
If you want to use Eloqua's WYSIWYG to make their responsive email you can do so, but I would recommend deleting all their body text before editing anything because of the inconsistencies in their code. Otherwise, I think you would be better off coding the emails outside of Eloqua using a 3rd party editor whether it's something more robust like Dreamweaver or Coda, or whether you feel comfortable working in a more text environment with programs like Notepad++ or Brackets.
At the end of the day remember you are paying Eloqua for these and if you choose to stick with the WYSIWYG and you are not getting the results you expect you need to tell Eloqua through your support channels.

What level CSS and HTML for Dreamweaver CS5 (Vers 11.0)

What level CSS and HTML for DW CS5?

CS5 does not support HTML5 in this sense -
1. It will not automatically start a new document with an HTML5 doctype (you can force it to do this - if you are interested I can tell you how), but you can always just replace what CS5 writes with an HTML5 snippet.
2. It will not show any of the new HTML5 tags in any of your menus (or in code hints) - if you want to do HTML5 you are on your own with manual coding.
The same is true with CSS - if you want to do any of the advanced CSS styles (like animation, gradients, rounded corners, shadows, etc.) you are on your own.

CSS and HTML not merging in design view

I hate questions that start with "all the sudden this happened."
I was using Dreamweaver CS5.5 along with some other things I had open. I was off doing something with one of the other things and came back to Dreamweaver. It was in design view not live view. All it shows me the HTML without merging the CSS that goes with it. However, when I hit Live View, it merges the code and displays just fine.
My machines been acting funny lately. Earlier today, Outlook kept shutting down, but that stopped. Some times my cursor moves strangely. Surely, this isn't a virus causing this with Dreamweaver. I run good protection and keep it updated.
I thought maybe IIS was not running, but it is. Without it, it probably would not have merged the CSS in live view. What could I possibly have done to this thing?

Thanks everybody, I did both of your suggestions to no avail. I looked and looked and couldn't find a reason for it. I had a backup of the files from a few days ago and I started replacing individual files to find the problem, but that got old. So I finally just copied in the whole backup and it's fine.
This had to be something creepy we'll never track down - not worth the time.
Thanks for trying.

Design view of CSS layout is innacurate

Hello all -
I'm beginning to redraft my company's hompage using a full
CSS layout instead of our current nested table layout. Since I need
to ensure that other staff members can edit pages freely - and I'm
the only person comfortable doing straight code - it's important
that the design view is as accurate as possible.
When editing in Dreamweaver 8, my three column layout (a left
table of contents, a center content column, and an additional
content right column) breaks so that the table of contents
dissapears. Some people have spoken with have suggested that my
problem might be the negative margins I'm using to position the
floated columns that form the meat of the page.
You can view the page here:
http://www.southernenvironment.org/test/home_redraft.html
The CSS is here:
http://www.southernenvironment.org/test/style_redraft.css
In addition, the header navbar also appears strangely. In
Design View, two word titles (ie. "Our Programs") break on to two
separate lines, instead of staying in one line as they do in
browsers I've tested.
The frustrating thing about this is that my design seems to
work in most browsers - but without a somewhat accurate
representation in Dreamweaver, I won't be able to sell the idea of
a standards-based revamp to other staff here.
Any ideas?
Matt

Your CSS is not tight enough to get accurate columns. You
shouldn't try to
define the columns with the body tag. For a purely CSS site,
you really find
out why the code is called 'cascading' styles. They cascade
all right. We've
just finished wrestling with a similar re-design with CSS and
the order of
how tags and files come into play is very important.
We have defined the body tag with background color, 0 margins
and font
family, color and size only. Header/footer and columns are
defined by ID.
The three "content" columns are within a page container,
header and footer
outside the page container. How these elements are placed is
important, as
they cascade.
We use 3 linked main css files, 1) Page Layout (3 or 4
different options) 2)
Page presentation (all text styles) 3) Page menu styles (only
menu styles).
They are in that order, as the only body tag is in Page
Layout.
If a page has a watermarked background we import the code
just for the
watermark.
This is not true for the home page, but all other pages in
the site.
http://www.nic.bc.ca/index.asp
I hope this helps.
Marianne
"homestar79" <[email protected]> wrote in
message
news:[email protected]...
> Hello all -
>
> I'm beginning to redraft my company's hompage using a
full CSS layout
> instead
> of our current nested table layout. Since I need to
ensure that other
> staff
> members can edit pages freely - and I'm the only person
comfortable doing
> straight code - it's important that the design view is
as accurate as
> possible.
>
> When editing in Dreamweaver 8, my three column layout (a
left table of
> contents, a center content column, and an additional
content right column)
> breaks so that the table of contents dissapears. Some
people have spoken
> with
> have suggested that my problem might be the negative
margins I'm using to
> position the floated columns that form the meat of the
page.
>
> You can view the page here:
>
>
http://www.southernenvironment.org/test/home_redraft.html
>
> The CSS is here:
>
>
http://www.southernenvironment.org/test/style_redraft.css
>
> In addition, the header navbar also appears strangely.
In Design View,
> two
> word titles (ie. "Our Programs") break on to two
separate lines, instead
> of
> staying in one line as they do in browsers I've tested.
>
> The frustrating thing about this is that my design seems
to work in most
> browsers - but without a somewhat accurate
representation in Dreamweaver,
> I
> won't be able to sell the idea of a standards-based
revamp to other staff
> here.
>
> Any ideas?
>
> Matt
>

Design View Issue Dreamweaver CS4 - Taking forever to load design view

I am having an issue where my site takes literally almost a full day to load in design view. Once it is loaded everything works seemlessly but once I close down Dreamweaver and reopen it, I have to wait another day to get to design view of my site. All files open just fine in code view.
I have deleted the Dreamweaver CS4 cache folder, completely formatted my drive and reinstalled creative suite. I have also validated my code on W3c and everything checks out fine.
The majority of my site is based off of a template, but even when I remove all the template references in the html files from Notepad I am still having the same issue. My site renders fine and quickly however on Explorer, Firefox, Chrome, and Safari.
When loading any other site off the web into Dreamweaver I do not run into the problem so there must be something wrong with how my site is set up. Either the Template file is no good or somewhere else I am falling short. Can someone, please, please, please ( I am begging) help me figure out what is going on here.
My index file is located at - http://www.thebluedot.net/index.html and the template file is located at - http://www.thebluedot.net/Templates/index.dwt
I have searched high and low and even made a post on this same topic about a month ago but never came up with a resolution to my issue. I had given up on finding a solution to this problem for some time, but I really need to figure out where I am going wrong here!
Additional Details -
I am running - Windows Vista Ultimate on a Core 2 Processor with 12 GB of Ram & Solid State Hard Drive. Everything on my system runs super smoothly except loading my site in Dreamweaver CS4 design view.
I really appreciate any help you can provide.

I have used CS2 Adobe GoLive to create and manage a website (pro-prosperity.com). Now, I have CS4 Dreamweaver. I got a new site set up on Dreamweaver using the site management facility. I then have the contents of website available locally on Dreamweaver. I can edit files. But the main home page, index.html, is not displaying on design view mode for editing, although it displays everything on live view mode. I have struggled for days and am not getting any difference in attributes of index.html and another .html that is displaying fine on design view and is editable.
I am really lost and am begging for any help. Can you, for example, copy the home page from pro-prosperity.com and display on design view and edit it? Please tell me what is in this file that is troublesome. Thanks.
The first thing you should do is to make sure that this feature is turned on (it's off by default):
View > Code View Options > Highlight Invalid Html
It's not perfect, but it will notify you of some problems. In Code View, there are many problems highlighted. Some of them don't make sense, but are triggered because of a problem with a parent tag.
Be sure to make a backup copy of your file before doing the next step. Close your page. Go to Preferences > Code Rewriting, and turn on "Fix invalidly nested and unclosed tags", "Remove extra closing tags", and "Warn when fixing or removing tags". Click OK, then re-open your page. The messages in the dialog to tell you what was changed. This allowed me to see your page in Design View (I am using CS5).
Note: I suggested that you reset your preferences to turn off those 3 settings as they can cause problems with some markup.
In the long term, I suggest that you avoid nesting tables wherever possible.
Hope this helps,
Randy

Dreamweaver CS4 Design View Issues

Hi,
I'm experiencing issues with the design view in DW CS4. It seems a little buggy to me. Sometimes I cannot seem to select any items at all, either using a single or double click. It's starting to drive me nuts. Is there an easy way to enter into this form of editing that's a little less random ?
Many thanks in advance

There are two things that could prevent you from editing a region of DW's design view:
The page is the child page of a DW template and the region you are trying to edit is in a NON-EDITABLE part of that template, and cannot be edited in the child page.
The container (i.e., the ancestor) for the region you are attempting to edit has a CSS style of "overflow:hidden" applied to it. Double clicking (or right click > Element View > View All) would open that region for editing.
If you are able to verify that one of those two possibilities is in play, then you have your answer. If neither of them applies, then we would need to see the page and its code - perhaps you could post a link to it?

Something's wrong...Design View issue....

OK.
I'm attempting to take an Excel purchase order form and turn it into an HTML form for a custom demo that I will be performing tomorrow. The nature of the demo isn't important; what is important is that I have no choice but to use Design View, as I need to make sure the HTML version is visually identical to the Excel version. Everything was going fine...until I glanced over into the code and noticed that instead of intuitively assuming that there should be one FORM element for multiple INPUT elements, Dreamweaver created a separate FORM element for each INPUT. So of the 15 elements I've got so far it created a separate FORM element for each. This is a problem, because the form won't submit properly in this fashion.
So I did the logical thing: Went into the code, removed the extra FORM elements, and migrated one of them to just after the BODY tag but before the actual content, then added the end tag at the tail end of it all. What happened next is my problem: Design View is all kinds of whacked out. It's not abiding by any of the table structures, background colors, anything. The code is correct - previewing the page verifies this. Firefox is about 95% accurate, and I can live with that threshold. IExplorer is about 85% accurate, and I can fix what's not correct, but it's way more accurate than Design View which just doesn't render it correctly at all. If I do Live View it's fine, but I can't edit WYSIWYG in that view. Now I'm stuck unless I "screw up" the code again, which I don't want to do.. I don't have any fancy scripts, nothing out of the ordinary...just regular tables, inputs and a few background colors rendered via CSS. I haven't even gotten halfway through the project yet.
Does anyone know why Dreamweaver does this? Why would Design View's rendering of simple tables be so astronomically different from what the browser sees? Is the Design View rendering engine too structured or something? See pics.
This is WRONG.
This is RIGHT.

I would think Design should show me what IE is seeing, at the very least.
This isn't FrontPage, you know? I'm pretty sure DW Design View uses a WebKit rendering engine, aka Safari & Chrome.
for whatever reason Dreamweaver won't allow me to apply proper styling (background colors, font sizes, etc) without going CSS. It's quite annoying.
CSS is not some arbitrary method fashioned by Adobe to make your life harder. It is in fact a web standard recommended by the W3C to make the web better for everyone.
The separation of Content (HTML) from Style (CSS) is not a brand new concept either. It's been around since the late 1990's.
To appreciate what CSS can do for you, visit the CSS Zen Garden.
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
http://alt-web.com/
http://twitter.com/altweb

Problem with CSS and HTML

I don't understand what is wrong but I don't see the styles when I preview my html in chrome.
Here's my CSS
@charset "UTF-8";
/* CSS Document */
html {
          min-width: 768px;
body {
          font-size: 100%;
          font-family: Arial, Helvetica, sans-serif;
          line-height: 1.5rem;
.wrapper {}
img {
          width: 100%; /*All images will be 100% the size of their parent */
.baseline {
          background-image: url(../images/baseline.svg);
strong {
          font-weight: bold;
em {
          font-style: italic;
/* ----------------------------------------------------------------------------------------- ------------- Masthead */
.masthead {
          height: 6rem;
          background-color: rgba(51,153,255,1);
          margin-bottom: 1,5rem;
h1 {
          font-size: 1.5rem;
          color: #9F6;
          position: absolute;
          margin: 2.25rem 0 0 4%;
/*---------------------------------------------------------------------------------------- --------------------article --*/
article {
          padding: 0 4% 1.5rem;
.headline {
          height: 4.5rem;
          margin-bottom: 1.5rem;
          background-colour: rgba(0,0,0,.15)
h2 {
          font-family:Georgia,"Times New Roman", Times, serif;
          font-size: 2.25rem;
          position: absolute;
          margin: 1.5rem 2% 0;
.placeholder {
          width: 20%;
          flow: left;
          margin: 0 2.5% 1.5rem 0;
p {
          margin-bottom: 1.5rem;
.footnote {
          height: 4.5rem;
          background-color: rgba(0,0,0,.15)
.footnote p {
          font-size: .875rem;
          position: absolute;
          margin: 1.5rem 2% 0;
/*---------------------------------------------------------------------------------------- -------------------- Bottom --*/
.Bottom {
          height: 15rem;
          background-color: rgba(51,153,255,1);
.bottom p {
          font-sizes: .875rem;
          color; #FFF;
          position:absolute;
          margin: 1.5rem 4%
Here's my HTML
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
<title>Box Model Tutorial</title>
<link href="box-model/reset.css" rel="stylesheet">
<link href="box-model/general.css" rel="stylesheet">
</head>
<body class="baseline">

                  <header class="masthead baseline"> 
                                <h1>Victoria</h1>

           <div class="wrapper">
                         <article>
                          <header class="headline">
                                    <h2>Tourism British-Columbia</h2>
                          </header>
                               <img src="box-model/images/images/British_Columbia_Legislative_Building,_Victoria,_BC_Wallpape r_2c8nm-1.jpg" alt="box-model/images/images/British_Columbia_Legislative_Building,_Victoria,_BC_Wallpape r_2c8nm-1.jpg">
                                
                                <p>The capital city of British Columbia, Victoria boasts many historic buildings and some of the most fascinating museums in Western Canada. The city benefits from one of Canada's mildest climates, which allows its residents to pursue outdoor pleasures all year round.
Victoria enjoys some of the country's most exhilarating scenery: there's an ocean or mountain vista around every corner, while the city's flower gardens are famous the world over. Whether your taste runs to golfing, hiking, biking and fishing or you're more the shopping, dining and theatre type, there are no end of delights for you and your family in Victoria – the city was included in the Top 10 Family Vacations in Canada in the TripAdvisor 2011 Travelers' Choice awards.
Established in 1843 by James Douglas as a fort for the Hudson's Bay Company, Victoria's British ancestry is apparent in the double-decker buses, horse-drawn carriages, formal gardens, and tearooms. The city is now a cosmopolitan centre with a lively entertainment scene and a wonderful array of attractions.</p>
               <footer class="footnote">
                                     <p> Article Footer (Related Articles, Footnotes, Authors Bio, etc.) </p>
                                 </footer>
                      </article>
                       </div> 

    <footer class="bottom">
             <p>Main Footer (Copyright, related Links, Legal, privacy, logo, etc.)</p>
    </footer>
</body>
</html>

Lines 6 & 7 of your HTML file (exercise-boxmodel.html), change this:
<link href="box-model/reset.css" rel="stylesheet">
<link href="box-model/general.css" rel="stylesheet">
to this:
<link href="reset.css" rel="stylesheet">
<link href="general.css" rel="stylesheet">
Your CSS files are in the same folder as your .html file. But your original linkage shows that they're within a sub-folder called 'box-model'. That link was returning a 404 Not found error. Hence, the browser was unable to load your CSS files.
Replace the code and you should be able to view it.

Style Message in design view with Apache Trinidad HTML components

Hi !!!
I'm using Apache Trinidad HTML components. In that components after using Table Layout I'm trying to use Row layout after dragging the row layout to the design view the following message is appearing in the design view, the same is happening in the browser window also.
style="position:absolute;width:auto;height:auto;top:0px;left:0px;bottom:0px;right:0px"
Thanks in Advance
Anil Kumar Golla

Ric,
First I created an application by selecting New Application from the Application Navigator. In that application window I submitted relevant names for creating the new application, after that it displayed the project window in that I given the project name then in Jdeveloper's Application window the project name is displayed from there I selected new by right clicking, in that New gallery window, I selected Web Tier > Page Template > Ok. In the Create Jsf Page template window I created a File Name and Facet Definitions namely North, West, East, South and Center. After that Jdeveloper created the new JSPX page. In that page first I dragged panel stretch layout from Adf Faces to the Jdeveloper's design view and given facet references (North, West, East, South and Center). In the North Portion I dragged the Apache Trinidad HTML's Table Layout component, after that Row layout, then in the design window I'm getting the "style="position:absolute;width:auto;height:auto;top:0px;left:0px;bottom:0px;right:0px". The same is displaying in the browser window also.
Thanks in Advance
Anil Golla

Design View issue

I've imported an older Flex 3 project into Flash Builder 4 Beta 2 and have the 'Use Flex 3 compatibility mode' is turned on. All is fine until I select 'MX Only' as the Component Set. Switching from 'MX + Spark' causes the Design View to become completely grey. Literally, there is nothing but solid grey. As I don't need the Spark components (which add an extra 200k to my Export Release I want to keep using only MX for now.
Help?

The only way I'm able to use Design View with my Flex 3 project is to set the Component Set to 'MX+ Spark'. Choosing only 'MX' will result in solid grey. As I don't need the Spark components I need to switch to the 'MX' Component Set each time I want create a release build. If there is any fast patch (or technique) to resolve this under Beta 2 please let me know. I would sure like to see things like this resolved for the release of Flash Builder 4. Otherwise, however, I'm happy to see that the import process of Flex 3 projects has become more seamless. Very nice.
Jason Villmer

Design View blank, JSP and Java views fine

I'm running JSC 2.1, I have 2 gig of memory. I'm not able to see the design view on one of my jsps, but the error message in the log isn't very helpful.
I did a cut-and-paste from another jsp view in another file -- is there something else I have to copy? If so, what and where to?
Any help appreciated.
Stack trace is below (I get five of the same errors with different line numbers; I'm only including one stack trace here):
java.lang.NullPointerException
at com.sun.rave.designer.DesignerTopComp.componentShowing(DesignerTopComp.java:868)
at org.netbeans.core.multiview.MultiViewPeer.showCurrentElement(MultiViewPeer.java:233)
at org.netbeans.core.multiview.MultiViewPeer.showCurrentElement(MultiViewPeer.java:205)
at org.netbeans.core.multiview.MultiViewPeer$SelectionListener.selectionChanged(MultiViewPeer.java:480)
at org.netbeans.core.multiview.MultiViewModel.fireSelectionChanged(MultiViewModel.java:224)
at org.netbeans.core.multiview.MultiViewModel.setActiveDescription(MultiViewModel.java:93)
at org.netbeans.core.multiview.MultiViewModel$BtnGroup.setSelected(MultiViewModel.java:274)
at javax.swing.JToggleButton$ToggleButtonModel.setSelected(JToggleButton.java:215)
at javax.swing.ButtonGroup.setSelected(ButtonGroup.java:139)
at org.netbeans.core.multiview.MultiViewModel$BtnGroup.setSelected(MultiViewModel.java:270)
at javax.swing.JToggleButton$ToggleButtonModel.setSelected(JToggleButton.java:215)
at javax.swing.JToggleButton$ToggleButtonModel.setPressed(JToggleButton.java:250)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
at java.awt.Component.processMouseEvent(Component.java:5488)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
at java.awt.Component.processEvent(Component.java:5253)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3955)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1774)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
[catch] at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

I figured out the problem. The Java code had gotten out of sync with the jsp code, so the design view didn't know how to render the components. It's a pain to fix, but it can be done. Go through your jsp code component by component, and make sure there are declarations, getters, and setters for each id in the components. Also make sure the java code doesn't contain declarations, getters, and setters for any components that you didn't create (you can see these in the jsp view at the bottom of the file).

Share the view wtih GAF and HTML

Hello All,
I have Benefits enrollement application to be designed such that the screen is shared with GAF and a HTML. The HTML is a page designed and will remain the same through out all the steps in GAF.
Please look at the picture attached.
The left part of the screen is a GAF component. The complete component is configured as required an working perfect.
The right part of the screen is a HTML. This will be added as a Freestyle UIBB with the WD Component and the Window details.
I am confused on how to bring them together on a single screen. Both of them are working perfectly fine.
Please let me know on how to solve the same.
Thanks,
Krishna.

Hi Maupatt,
Here is an article I found using the Data View Web Part.
http://dougortiz.blogspot.com/2009/06/displaying-and-filtering-lists-in.html
You can also use the content query webpart for this, but this is just for displaying content not for manipulation.
Regards
Pieter
Regards, Pieter
MCPD | MCITP
My Blog
Please remember to click "Mark As Answer" if a post solves your problem or "Vote As Helpful" if it was useful.

Various bugs – Library view issue / import and copy problem / unsupported paths message

In addition to the issues reported in a separate thread regarding importing video, there are several other bugs that are preventing me from progressing on a project and/or indicate instability in Edge Animate. These issues don’t occur on new projects (yet), but are present in my current composition.
I'm using the latest version of Edge Animate CC 2014 (2014.1.1) on a Windows 8 Pro (fully updated) system.
Issue 1 – Library View
For all the assets that have been imported, when I twirl down to view the thumbnail of each asset in the Library, nothing appears in the thumbnail area. In earlier iterations of this project, all the items appeared correctly, but now nothing is there for any of the assets. See sample below of what should appear (and what was there before), and what’s there now (nothing).
Issue 2 – Asset Import Problem
When I try to add an already imported image asset to the stage (or try to import a new image asset in the project), the item doesn’t appear properly – it just comes in as a dot with no height or width. See samples below of what the imported asset looks like on the stage and its size information.
Assets that were imported and placed before this bug occurred are still visible on the stage. But, if I copy one of these assets, the copy retains the size information, but does not appear at all. See sample.
Issue 3 – Unsupported Paths message
When I close the project, I get an unsupported paths message. See sample.
Despite this message, the assets appear in the project from within Edge and are present in the project if I open/preview the HTML file in my browser.
Since these three issues relate to project assets, perhaps they are related. I can provide a link to download this project if you like. Any help would be greatly appreciated!

Hi Avinash,
I'm glad you received the (large) project.
In the meantime, I installed Edge Animate on another system (OS - Windows 8.1). The Edge project exhibits the same problems on the other system.
Thanks for looking into this!
Regards,
- Joel

ASP in 'Design View' Issues

I'm trying to add ASP includes that I created in DW using
simple HTML and saving it out as ASP into a ASP Page in DW that
originally came from FrontPage :( When I include these ASP includes
I loose the visual of all my elements when I'm working in the
Design and Code View. Which I would rather edit in Design that
Code.
FYI: When I brought the original ASP page from Frontpage in
DW I was able to VIew the html elements and had the ASP icon in the
corresponding ASP includes which is perfect.
Please any help would be great. Obviously I have been thrown
into a programmers world and I'm drowning. :)

It sounds like your includes are full HTML pages and not just
snippets. The
includes cannot have <head>, <html>, or
<body> tags anywhere.
"hairpeace65" <[email protected]> wrote in
message
news:f32bi9$i8v$[email protected]..
> I'm trying to add ASP includes that I created in DW
using simple HTML and
> saving it out as ASP into a ASP Page in DW that
originally came from
> FrontPage
> :( When I include these ASP includes I loose the visual
of all my
> elements
> when I'm working in the Design and Code View. Which I
would rather edit in
> Design that Code.
>
> FYI: When I brought the original ASP page from Frontpage
in DW I was able
> to
> VIew the html elements and had the ASP icon in the
corresponding ASP
> includes
> which is perfect.
>
> Please any help would be great. Obviously I have been
thrown into a
> programmers world and I'm drowning. :)
>
>

Design view issue - CSS and html

Similar Messages

Maybe you are looking for