Design view no styling
Hi
Recently, and I do not think it is specific to an update, Dreamweaver 2014.1.1 build 6981 is opening files and in the design view all styles are not rendering. Do all my fonts are default face and black and links blue. I work in e-mail marketing and my font styles are mainly in-line css. I want to see the proper font-face, color and link styling.
After I do some editing all of a sudden the styling sometimes pops in place. When I preview in browser all looks fine but this is annoying me. It feels like a step backwards. Is there some setting involved for design view to be an actual design view?
I am in Windows 7 service pack1 with an i7 processor and12 GB ram so it isn't a processing issue I am sure.
Thanks
RL
That's usually a sign of an error somewhere in your code that DW is having issue with. The newer versions seem to be a bit more picky about code issues. Run your pages through the validators at...
HTML: http://validator.w3.org/
CSS: http://jigsaw.w3.org/css-validator/
And make sure you don't have any major structural errors like missing end tags in your html or missing semi-colons or curly brackets in your css.
Similar Messages
-
Table td not styling correctly in Design View CS4
Hello everyone!
I dont know if anyone else is experiencing this problem, or
if I'm doing something stupid! I've searched all over this forum
and google etc and found a few people with similar problem but no
solution.
please see this code (HTML first, then the external CSS file)
The code is complete, not truncated or stripped. In IE and
Firefox, the CSS body styling renders on all text outside the table
and inside the table (which I believe is correctly inherited) but
in CS4 Design View, the text inside the table renders at twice the
size!!
I'm doing a complex page and it's pushing all my elements
around in Design View and preventing me from working properly or at
times at all!!
Please tell me if this is a bug or is there something I can
do to stop it displaying like this.
Thank you!
Janine xOn Fri, 3 Apr 2009 09:29:57 +0000 (UTC), "Janine_Trumel"
<[email protected]> wrote:
> Sorry, I cant quite see why the first line of code is
causing the problem.
Regarding the XML declaration that Nancy suggested omitting,
the XHTML
specs suggest using the line, but it is not required if the
page uses
either UTF-8 or UTF-16 character encoding. See
http://www.w3.org/TR/xhtml1/#strict
where is says in part, "An XML
declaration is not required in all XML documents; however
XHTML document
authors are strongly encouraged to use XML declarations in
all their
documents. Such a declaration is required when the character
encoding of
the document is other than the default UTF-8 or UTF-16 and no
encoding was
determined by a higher-level protocol."
IE only pays attention to the DOCTYPE if it is the very first
thing in the
page. Put anything before the doctype and IE will drop to
quirks mode.
That's just an IE bug that you'll have to live with.
Gary -
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/ -
Certain images not showing up in Design View
Hi,
I recently switched from Dreamweaver CS5.5 to CS6 with Creative Cloud but now some of my images aren't showing up in Design View. Everything is fine in Live View.
Any help would be gratefully received. I have attached the CSS & the HTML as well as two screen shots of Design View and Live View.
The CSS is:
/* Getting the new tags to behave */
article, aside, audio,
canvas, command,
datalist, details,
embed,
figcaption, figure, footer,
header, hgroup,
keygen,
meter,
nav,
output,
progress,
section, source,
video {
display:block;
mark,
rp, rt, ruby,
summary,
time {
display:inline;
/* Global properties ======================================================== */
body {
background-color:#000;
background-repeat:no-repeat;
background-position:center top;
background-image:url(../images/body-bg.jpg);
background-attachment:fixed;
font-family:Arial, Helvetica, sans-serif;
font-size:100%;
line-height:1em;
color:#949595;
html {
min-width:967px;
html,
body {
height:100%;
/* Global Structure ============================================================= */
#main {
margin:0 auto;
width:967px;
font-size:.75em;
/* Header */
header {
position:relative;
/* Sidebar */
aside {
width:227px;
float:left;
margin-right:32px;
padding-bottom:33px;
/* Content */
section#content {
float:left;
width:675px;
padding-top:6px;
/* Footer */
footer {
padding-left:3px;
background:url(../images/border-left.png) repeat-y left top;
color:#535353;
/* Left & Right alignment */
.fleft {
float:left;
.fright {
float:right;
.clear {
clear:both;
.col-1,
.col-2,
.col-3 {
float:left;
.alignright {
text-align:right;
.aligncenter {
text-align:center;
.wrapper {
width:100%;
overflow:hidden;
/*----- form defaults -----*/
input,
select,
textarea {
font-family:Arial, Helvetica, sans-serif;
font-size:1em;
vertical-align:middle;
font-weight:normal;
fieldset {
border:0;
/*----- lists -----*/
.banners {
width:100%;
overflow:hidden;
padding-bottom:15px;
.banners li {
float:left;
padding-left:4px;
.list li {
font-size:1.17em;
padding:0 0 19px 22px;
background:url(../images/marker.png) no-repeat left 2px;
.list li.last {
padding-bottom:0;
.list1 li {
width:100%;
overflow:hidden;
padding-bottom:27px;
.list1 li img {
float:left;
margin-right:22px;
.column-list {
width:100%;
overflow:hidden;
.column-list li {
float:left;
width:200px;
margin-right:27px;
.column-list li.last {
margin:0;
.column-list li img {
margin-bottom:18px;
.events-list {
width:100%;
overflow:hidden;
.events-list li {
float:left;
line-height:1.5em;
width:320px;
margin-right:25px;
padding-bottom:20px;
.events-list li.alt {
margin-right:0;
.events-list li img {
float:left;
margin-right:11px;
.testimonials li {
line-height:1.5em;
padding-bottom:18px;
.testimonials li cite {
font-style:normal;
.testimonials li h5 {
text-align:right;
margin:0;
padding-top:6px;
/*----- other -----*/
.img-indent {
margin:0 0 20px 0;
.extra-wrap {
overflow:hidden;
p {
margin-bottom:16px;
line-height:1.5em;
dl {
line-height:1.5em;
dl dt {
font-weight:bold;
color:#4b4b4b;
margin-bottom:6px;
dl dd {
padding-bottom:20px;
dl dd.last {
padding:0;
.address dd {
clear:both;
.address dd span {
float:left;
width:96px;
.address dd a {
font-size:1.17em;
address {
font-style:normal;
line-height:1.5em;
address a {
font-size:1.17em;
address span {
float:left;
width:103px;
/*----- txt, links, lines, titles -----*/
a {
color:#12b7f4;
outline:none;
a:hover {
text-decoration:none;
h1 {
font-size:20px;
line-height:1em;
font-weight:normal;
padding:55px 0 0 3px;
h1 a {
color:#fff;
text-decoration:none;
h1 strong {
font-size:55px;
line-height:1.2em;
letter-spacing:-2px;
top:-37px;
position:relative;
h2 {
font-size:1.917em;
line-height:1.2em;
letter-spacing:-1px;
font-weight:normal;
h5 {
font-size:1em;
line-height:1.5em;
color:#4b4b4b;
margin-bottom:6px;
h5 a {
color:#4b4b4b;
.txt1 {
font-size:1.17em;
.rss {
position:absolute;
right:18px;
top:18px;
background:url(../images/rss.gif) no-repeat right top;
padding:10px 45px 8px 0;
color:#7d7d7d;
text-decoration:none;
font-size:1.17em;
text-transform:uppercase;
.rss:hover {
text-decoration:underline;
.link1 {
display:block;
position:relative;
float:left;
background-repeat:no-repeat;
background-position:right top;
background-image:url(../images/link1-right.png);
color:#fff;
line-height:1.2em;
text-transform:uppercase;
text-decoration:none;
cursor:pointer;
.link1 span {
display:block;
float:left;
background-repeat:no-repeat;
background-position:left top;
background-image:url(../images/link1-left.png);
padding:0 10px;
.link1 b {
background-repeat:repeat-x;
background-position:left top;
background-image:url(../images/link1-bgd.png);
padding:8px 7px 9px 7px;
display:block;
float:left;
.link1:hover b {
text-decoration:underline;
.link2 {
width:70px;
height:30px;
text-align:center;
text-transform:uppercase;
color:#fff;
text-decoration:none;
display:block;
float:right;
font-weight:bold;
overflow:hidden;
line-height:2.6em;
background-repeat:no-repeat;
background-position:left top;
background:url(../images/link2-bg1.png);
.link2:hover {
text-decoration:underline;
/*==================boxes====================*/
.nav-box {
width:100%;
position:relative;
padding-bottom:11px;
margin-top:-23px;
.nav-box .left {
padding-left:20px;
background:url(../images/nav-box-left.png) no-repeat left top;
.nav-box .right {
padding-right:20px;
background:url(../images/nav-box-right.png) no-repeat right top;
.nav-box nav {
height:72px;
background:url(../images/nav-box-tail.png) repeat-x left top;
.nav-box nav ul {
padding-top:13px;
width:100%;
overflow:hidden;
.nav-box nav ul li {
float:left;
font-size:1.583em;
line-height:1.2em;
letter-spacing:-1px;
.nav-box nav ul li a {
color:#535353;
display:block;
float:left;
cursor:pointer;
background:url(../images/spacer.gif);
text-decoration:none;
text-shadow:#fff 1px 1px;
.nav-box nav ul li a:hover,
.nav-box nav ul li a.active {
color:#fff;
background:url(../images/nav-act-tail.gif) repeat-x left top;
text-shadow:#fff 0 0;
.nav-box nav ul li a span {
display:block;
float:left;
background:url(../images/spacer.gif);
.nav-box nav ul li a:hover span,
.nav-box nav ul li a.active span {
background:url(../images/nav-act-left.gif) no-repeat left top;
.nav-box nav ul li a b {
display:block;
float:left;
background:url(../images/spacer.gif);
padding:10px 23px 14px 23px;
.nav-box nav ul li a:hover b,
.nav-box nav ul li a.active b {
background:url(../images/nav-act-right.gif) no-repeat right top;
.box {
width:237px;
color:#fff;
.box .top {
background-repeat:no-repeat;
background-position:left top;
background-image:url(../images/box-top.png);
height:14px;
overflow:hidden;
font-size:0;
line-height:0;
.box .bot {
background-repeat:no-repeat;
background-position:left top;
background-image:url(../images/box-bot.png);
height:15px;
overflow:hidden;
font-size:0;
line-height:0;
.box .xcontent {
background-repeat:repeat-y;
background-position:left top;
background-image:url(../images/box-tail.gif);
.box .xcontent .bg {
min-height:137px;
height:auto!important;
height:137px;
background-repeat:no-repeat;
background-position:left top;
background-image:url(../images/box-bg.jpg);
.box .inner {
padding:2px 35px 0 26px;
.box h2 {
font-size:2.417em;
font-weight:bold;
margin-bottom:4px;
text-shadow:#0b97e4 1px 1px;
.box p {
line-height:1.583em;
margin-bottom:9px;
/* box style1 */
.box.style1 .top {background-image:url(../images/box-top1.png);}
.box.style1 .bot {background-image:url(../images/box-bot1.png);}
.box.style1 .xcontent {background-image:url(../images/box-tail1.gif);}
.box.style1 .xcontent .bg {background-image:url(../images/box-bg1.jpg);}
.box.style1 .link1 {background-image:url(../images/link1-right1.png);}
.box.style1 .link1 span {background-image:url(../images/link1-left1.png);}
.box.style1 .link1 b {background-image:url(../images/link1-bgd1.png);}
.box.style1 h2 { text-shadow:#78b10b 1px 1px;}
/* box style2 */
.box.style2 .top {background-image:url(../images/box-top2.png);}
.box.style2 .bot {background-image:url(../images/box-bot2.png);}
.box.style2 .xcontent {background-image:url(../images/box-tail2.gif);}
.box.style2 .xcontent .bg {background-image:url(../images/box-bg2.jpg);}
.box.style2 .link1 {background-image:url(../images/link1-right2.png);}
.box.style2 .link1 span {background-image:url(../images/link1-left2.png);}
.box.style2 .link1 b {background-image:url(../images/link1-bgd2.png);}
.box.style2 h2 { text-shadow:#ff6900 1px 1px;}
/* box style3 */
.box.style3 .top {background-image:url(../images/box-top3.png);}
.box.style3 .bot {background-image:url(../images/box-bot3.png);}
.box.style3 .xcontent {background-image:url(../images/box-tail3.gif);}
.box.style3 .xcontent .bg {background-image:url(../images/box-bg3.jpg);}
.box.style3 .link1 {background-image:url(../images/link1-right3.png);}
.box.style3 .link1 span {background-image:url(../images/link1-left3.png);}
.box.style3 .link1 b {background-image:url(../images/link1-bgd3.png);}
.box.style3 h2 { text-shadow:#ffad07 1px 1px;}
.box1 {
width:227px;
.box1 .top {
height:49px;
overflow:hidden;
background:url(../images/box1-top.png) no-repeat left top;
.box1 .bot {
height:17px;
font-size:0;
line-height:0;
overflow:hidden;
background:url(../images/box1-bot.gif) no-repeat left top;
.main-box .box1 .border-left {
padding-left:1px;
background:url(../images/box1-border.gif) repeat-y left top;
.main-box .box1 .border-right {
padding-right:1px;
background:url(../images/box1-border.gif) repeat-y right top;
.main-box .box1 .xcontent {
width:100%;
min-height:261px;
height:auto!important;
height:261px;
padding:0;
background:url(../images/box1-tail.gif) repeat-x left top #f8f8f8;
.main-box .box1 .inner {
padding:12px 14px 20px 18px;
.box1 h2 {
font-weight:bold;
color:#fff;
padding:10px 0 0 18px;
.box2 {
width:227px;
.box2 .top {
height:15px;
overflow:hidden;
background:url(../images/box2-top.png) no-repeat left top;
.box2 .bot {
height:16px;
font-size:0;
line-height:0;
overflow:hidden;
background:url(../images/box2-bot.gif) no-repeat left top;
.main-box .box2 .border-left {
padding-left:1px;
background:url(../images/box2-border.gif) repeat-y left top;
.main-box .box2 .border-right {
padding-right:1px;
background:url(../images/box2-border.gif) repeat-y right top;
.main-box .box2 .xcontent {
width:100%;
min-height:113px;
height:auto!important;
height:113px;
padding:0;
background:url(../images/box2-tail.gif) repeat-x left top #f6f6f6;
.main-box .box2 .inner {
padding:0 14px 20px 18px;
.box2 h2 {
font-weight:bold;
color:#3c3c3c;
margin-bottom:16px;
.main-box {
width:100%;
.main-box .left-top-corner {
background:url(../images/left-top-corner.png) no-repeat left top;
height:18px;
padding-left:18px;
.main-box .right-top-corner {
background:url(../images/right-top-corner.png) no-repeat right top;
height:18px;
padding-right:18px;
.main-box .border-top {
background:url(../images/border-top.png) left top repeat-x;
height:18px;
font-size:0;
line-height:0;
width:100%;
.main-box .border-left {
background:url(../images/border-left.png) left top repeat-y;
padding-left:3px;
.main-box .border-right {
background:url(../images/border-right.png) right top repeat-y;
padding-right:3px;
.main-box .xcontent {
background:#fff;
padding:0 2px;
.main-box .tail {
background:url(../images/main-box-tail.gif) repeat-x left top;
width:100%;
.main-box .inner {
padding:3px 15px 0 8px;
.main-box .inner1 {
padding:3px 8px 0 25px;
.main-box .inner1 aside {
margin:0;
.main-box .inner1 #content {
margin-right:32px;
width:665px;
.main-box .inner2 {
padding:3px 25px 35px 25px;
.main-box .inner2 #content {
width:auto;
float:none;
/*===== content =====*/
#content h2 {
color:#3e3e3e;
letter-spacing:0;
margin-bottom:16px;
#content .indent {
padding-bottom:60px;
#content .link2 {
background-image:url(../images/link2-bg2.png);
float:left;
/*===== Sidebar =====*/
aside .indent {
margin-bottom:20px;
/*===== footer =====*/
footer .right {
padding-right:3px;
background:url(../images/border-right.png) repeat-y right top;
footer .tail {
padding:17px 0 11px 27px;
background-color:#2d2d2d;
footer .line-ver {
background:url(../images/divider.gif) repeat-y 210px 0;
width:100%;
overflow:hidden;
footer .fleft a {
color:#535353;
text-decoration:none;
footer .fleft a:hover {
text-decoration:underline;
footer .fleft {
padding-bottom:8px;
footer .fleft ul {
padding:8px 0 3px 0;
footer .fleft ul li {
display:inline;
footer .fright {
padding:0 29px 0 0;
text-align:right;
footer .fright a {
color:#12b7f4;
footer .fright ul {
padding:8px 0 5px 0;
footer .fright ul li {
display:inline;
padding-right:15px;
margin-right:12px;
background:url(../images/divider1.gif) no-repeat right 3px;
footer .fright ul li a {
text-decoration:none;
color:#535353;
footer .fright ul li a:hover,
footer .fright ul li a.active {
color:#c4c4c4;
text-decoration:underline;
footer .fright ul li.last {
background:none;
padding:0;
margin:0;
/*----- forms -----*/
#subscribe-form .rowElem {
width:100%;
overflow:hidden;
#subscribe-form span {
display:block;
width:193px;
height:26px;
margin-bottom:6px;
background:url(../images/input-bg.png) no-repeat left top;
#subscribe-form input {
background:none;
border:0;
line-height:1.2em;
vertical-align:top;
margin:5px 0 0 10px;
color:#8c8d8d;
width:173px;
#subscribe-form a.fleft {
color:#4b4b4b;
font-weight:bold;
position:relative;
left:10px;
top:7px;
/* The Nivo Slider styles */
#slider_box{ width:946px; height:370px; margin-top:-3px; margin-bottom:15px;background:url(../images/bg_img.png) 0 0 no-repeat; padding:21px 0 0 21px}
#slider{ position:relative; width:925px; height:348px; z-index:88;overflow:hidden;}
/* If an image is wrapped in a link */
.nivoSlider a.nivo-imageLink {position:absolute;top:0px;left:0px;width:100%;height:100%;border:0;padding:0; margin:0;z-index:60;display:none;}
/* The slices in the Slider */
.nivo-slice {display:block; position:absolute;z-index:50;height:100%;}
/* Direction nav styles (e.g. Next & Prev) */
.nivo-directionNav a { position:absolute; bottom:-34px; z-index:99; cursor:pointer;text-indent:-5000px; width:30px; height:30px; display:block;}
.nivo-prevNav { right:135px; background:url(../images/marker_left.gif) no-repeat}
.nivo-prevNav:hover{ background:url(../images/marker_left_active.gif) no-repeat}
.nivo-nextNav {right:10px; background:url(../images/marker_right.gif) no-repeat}
.nivo-nextNav:hover{ background:url(../images/marker_right_active.gif) no-repeat}
/* Control nav styles (e.g. 1,2,3...) */
.nivo-controlNav{ position: absolute;z-index:99; right:14px; bottom:21px;}
.nivo-controlNav a {position:relative;z-index:99;cursor:pointer; text-indent:-5000px; width:16px; height:16px; float:left; margin-right:6px; background:url(../images/buttons.png) right 0 no-repeat}
.nivo-controlNav a.active { background-position:left}
/* Caption styles */
.nivo-caption { padding-top:77px; height:270px; width:345px;position:absolute; top:0px; right:20px; color:#fff; z-index:99;}
.nivo-caption .box{ display:inline-block;background:url(../images/box.png) no-repeat; font:24px Arial, Helvetica, sans-serif; color:#fff; line-height:30px; text-align:center; font-weight:bold; width:83px; margin-right:10px;}
.nivo-caption .text1{ font:36px Arial, Helvetica, sans-serif; color:#39c0f8; font-weight:bold; display:inline-block; line-height:1.2em; margin-top:-7px;}
.nivo-caption .text2{ font:48px Arial, Helvetica, sans-serif; color:#fff; font-weight:bold; display:block; line-height:1.2em; margin-top:-10px; letter-spacing:-2px;}
.nivo-caption p{ font-size:12px; color:#fff; line-height:14px; font-weight:bold; padding-top:8px;}
.nivo-caption a{ display:inline-block; position:absolute; left:0; bottom:60px; background:url(../images/button-bg.png) 0 0 no-repeat; font:40px Arial, Helvetica, sans-serif; line-height:60px; padding-bottom:3px; text-align:center; width:194px; color:#fff; text-decoration:none; letter-spacing:-2px;}
.nivo-caption a:hover{ background-position:bottom}
.color1 p{ color:#454545}
.nivo-caption .color1 .text1{ font-size:30px; display:block; color:#454545; margin-top:0}
.nivo-caption .color1 .text2{ color:#3b3b3b; display:inline-block; letter-spacing:-3px}
.nivo-caption .color1 .box{ margin-right:0px; margin-top:7px; margin-left:7px}
#contacts-form .rowElem {
height:40px;
#contacts-form .rowElem span {
display:block;
width:300px;
height:26px;
margin-bottom:6px;
background:url(../images/input-bg_2.png) no-repeat left top;
#contacts-form input {
background:none;
border:0;
line-height:1.2em;
vertical-align:top;
margin:5px 0 0 10px;
color:#8c8d8d;
width:300px;
#contacts-form .rowElem1 span {
display:block;
width:300px;
height:175px;
margin-bottom:21px;
background:url(../images/textarea-bg.gif) no-repeat left top;
#contacts-form textarea {
width:300px;
height:168px;
overflow:auto;
background:none;
border:0;
color:#8c8d8d;
padding:5px 0 2px 10px;
#contacts-form .link2 {
margin-left:15px;
/*==========================================*/
The HTML is:
<!DOCTYPE html>
<html lang="en">
<head>
<!-- TemplateBeginEditable name="doctitle" -->
<title>TravelSober.com Eastern Caribbean Sober Cruise</title>
<meta name="keywords" content="Sober cruise, sober cruises, sober cruise vacations, sober holidays, sober travel, sober vacation, sober vacations, aa convention, sober safari, sober travel.">
<meta name="description" content="Find out more about our Eastern Caribbean Sober Cruise or any of our other sober vacations.">
<!-- TemplateEndEditable -->
<meta charset="utf-8">
<link rel="stylesheet" href="css/reset.css" type="text/css" media="all">
<link rel="stylesheet" href="css/layout.css" type="text/css" media="all">
<link rel="stylesheet" href="css/style.css" type="text/css" media="all">
<!--[if lt IE 7]>
<link rel="stylesheet" href="css/ie/ie6.css" type="text/css" media="screen">
<script type="text/javascript" src="js/ie_png.js"></script>
<script type="text/javascript">
ie_png.fix('.png, .nav-box .left, .nav-box .right, nav, footer .right, footer, #slider, #slider .inside a, .box .top, .box .bot, .link1, .link1 span, .link1 b, .list li, .main-box .left-top-corner, .main-box .right-top-corner, .main-box .border-top, .main-box .border-left, .main-box .border-right, .box1 .top, .box2 .top, .link2, .link3, .events-list li img, #subscribe-form span');
</script>
<![endif]-->
<!--[if lt IE 9]>
<script type="text/javascript" src="js/html5.js"></script>
<![endif]-->
<style type="text/css">
body,td,th {
font-size: 92%;
</style>
<!-- TemplateBeginEditable name="head" -->
<!-- TemplateEndEditable -->
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-21210386-3']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
</script>
<link href="images/favicon.ico" rel="SHORTCUT ICON">
</head>
<body id="page7">
<div id="main">
<!-- header -->
<header>
<h1><a href="index.html"><strong>TravelSober.com</strong></a></h1>
<div class="nav-box">
<div class="left">
<div class="right">
<nav>
<ul>
<li><a href="index.html"><span><b>Home</b></span></a></li>
<li><a href="about-us.html"><span><b>About Us</b></span></a></li>
<li><a href="planned-trips.html"><span><b>Planned Trips</b></span></a></li>
<li><a href="instant-specials.html"><span><b>Bob's Super Specials</b></span></a></li>
<li><a href="testimonials.html"><span><b>Testimonials</b></span></a></li>
<li><a href="contact-us.html"><span><b>Contact Us</b></span></a></li>
</ul>
</nav>
</div>
<a href="#" class="rss">RSS</a> </div>
</div>
<ul class="banners">
<li>
<div class="box">
<div class="top"></div>
<div class="xcontent">
<div class="bg">
<div class="inner">
<h2>Sober Cruises</h2>
<p>Our cruises go to the best destinations on earth on a budget or in 6 Star luxury.</p>
<div class="wrapper"><a href="planned-cruises.html" class="link1"><span><b>more</b></span></a></div>
</div>
</div>
</div>
<div class="bot"></div>
</div>
</li>
<li>
<div class="box style1">
<div class="top"></div>
<div class="xcontent">
<div class="bg">
<div class="inner">
<h2>Friends of Lois Trips</h2>
<p>Al-Anon conferences and vacations</p>
<div class="wrapper"><a href="friends-of-lois-trips.html" class="link1"><span><b>more</b></span></a></div>
</div>
</div>
</div>
<div class="bot"></div>
</div>
</li>
<li>
<div class="box style2">
<div class="top"></div>
<div class="xcontent">
<div class="bg">
<div class="inner">
<h2>Conventions</h2>
<p>We take advantage of the many worldwide AA conventions combining them with tours.</p>
<div class="wrapper"><a href="sober-cruise-greece-2013.html" class="link1"><span><b>more</b></span></a></div>
</div>
</div>
</div>
<div class="bot"></div>
</div>
</li>
<li>
<div class="box style3">
<div class="top"></div>
<div class="xcontent">
<div class="bg">
<div class="inner">
<h2>Recovery</h2>
<p>Check out our sober resources page for all fellowships and the chance to meet new friends.</p>
<div class="wrapper"><a href="recovery-resources.html" class="link1"><span><b>more</b></span></a></div>
</div>
</div>
</div>
<div class="bot"></div>
</div>
</li>
</ul>
</header>
<div class="main-box">
<div class="left-top-corner">
<div class="right-top-corner">
<div class="border-top"></div>
</div>
</div>
<div class="border-left">
<div class="border-right">
<div class="xcontent">
<div class="tail">
<div class="inner2">
<!-- content -->
<section id="content">
<h2><b>Costa Caribbean Cruise on the Mediterranea
- November 30 – December 10, 2012</b><br><br>
<b>From $699 Per Person / Double-Occupancy. 10 days for the price of 7!</b></h2>
<p> <img src="images/costa-mediterranea-sober-cruise- caribbean-2012.jpg" alt="sober_cruise_caribbean" width="320" height="204" align="right"></p>
<h5>Enjoy the Bahamas, Jamaica, Grand Cayman Islands, Roatan, Belize and Cozumel with a round-trip from Miami. You will experience great Italian cuisine, fabulous entertainment and famous <i>In This Life</i> Custom Excursions. We will feature the best of snorkeling, scuba, golf, dolphin encounter and much more!<p></p>Get on board for one of our latest once in a lifetime opportunities. Costa Cruises has reached out to showcase their ships and famous Italian ambience. We have traveled extensively with Costa on one of their best vessels, the Mediterranea. <p></p>This is one of the most popular vessels in the Costa fleet and has been enjoyed by hundreds of <i>In This Life</i> clients. Costa has extended special rates because of the unfortunate accident in Europe. They are giving <i>In This Life</i> guests 10 days for the price of 7 with free upgrades on their November 30 combination Eastern-Western Caribbean cruise.<p></p>Join us for various meetings onboard everyday!</h5>
<h5>10-day itinerary includes: <dir>
<p>Day 1: Depart 9.00pm: Miami, Florida,<br>
Day 2: 9.00am - 6.00pm: Nassau, Bahamas,<br>
Day 3: At Sea,<br>
Day 4: 12.00pm - 7.00pm: Ochos Rios, Jamaica,<br>
Day 5: 9.00am - 6.00pm: Grand Cayman,<br>
Day 6: At Sea,<br>
Day 7: 8.00am - 6.00pm: Roatan, Honduras,<br>
Day 8: 8.00am - 5.00pm: Belize,<br>
Day 9: 8.00am - 7.00pm: Cozumel, Mexico,<br>
Day 10: At Sea,<br>
Day 11: Miami, Florida: Arrive 8.00am.</p>
</dir><h2>ITL special - Save up to $200 per person! These are exclusive prices ONLY AVAILABLE from <i>Travel Sober</i>. </h2>
<img src="images/Cribbean-sober-cruise-2012.jpg" alt="sober_cruise_caribbean" width="394" height="264" align="right">
<h5><p></p>Inside Cabin: $699<br>Ocean View Cabin: $699<br>Deluxe Ocean View Cabin: $899<br>Veranda Cabin: $899</p>
<p></p>
<p>Book an Inside Cabin for $699 and be upgraded for free to Ocean View.
<p></p>Book Deluxe Ocean View for $899 and be upgraded for free to Veranda.
Other free upgrades within categories – placement on first come, first served basis.
<p></p>This is a Sober Cruise. Get a group together and get extra PERKS!
</p>
<p><h2>Deposit now for best cabin placement, specials and free upgrades!</h2><br><br>
<img src="images/in-this-life-logo.jpg" alt="sober_cruise_caribbean" width="300" height="214" align="middle">
<h5><h2>
Call or Email Us Today</h2></a>
<p></p><h2>Office: (805) 927-6910</h2>
<h2>Toll Free: (800) 531-7578</h2>
<p></p><br>
<h2>Email:<a href="mailto:[email protected]" class="txt1"> [email protected]</h2></a><br>
<h2>Email:<a href="mailto:[email protected]" class="txt1"> [email protected]</h2></a>
</p></h5>
</section>
</div>
</div>
</div>
</div>
</div>
</div>
<!-- footer -->
<footer>
<div class="right">
<div class="tail">
The MORE buttons aren't images. They are in the HTML and appear to be styled with CSS to look like button images.
<span><b>more</b></span>
Unfortunately, Design View is incapable of displaying CSS border-radius, gradients, shadows and other CSS level 3 properties. That's why we have Live View which behaves more like a real browser.
If you can't live with this, disable CSS in DW by going to View > Style Rendering > untick display styles.
Or, use a Design-Time Style Sheet that contains no CSS level 3 properties.
Nancy O. -
Auto Inserting tags in Design View
Hi,
I keep running into a problem that is bugging the crap out of
me and I was hoping the Dreamweaver community could help me solve
it.
Whenever I am in Design View, and I add, say a table, then
type some text inside any of the cells, there is a opening and
closing p tag that automatically is added around the text.
p tags are no good for me because stylesheets in my CMS
controls the p tags and in order to avoid this from happening, I
would have to apply styling to every page, which obviously is
horribly inefficient. I figured Dreamweaver being the powerful
beast of a website editor it is, would have some option that allows
me to either turn this off entirely, or modify what gets added.
Could someone help me out?
Thanks!On Fri, 1 Aug 2008 20:00:44 +0000 (UTC), "bothead1"
<[email protected]> wrote:
>Hi,
>
> I keep running into a problem that is bugging the crap
out of me and I was
>hoping the Dreamweaver community could help me solve it.
>
> Whenever I am in Design View, and I add, say a table,
then type some text
>inside any of the cells, there is a opening and closing p
tag that
>automatically is added around the text.
>
> p tags are no good for me because stylesheets in my CMS
controls the p tags
>and in order to avoid this from happening, I would have
to apply styling to
>every page, which obviously is horribly inefficient. I
figured Dreamweaver
>being the powerful beast of a website editor it is, would
have some option that
>allows me to either turn this off entirely, or modify
what gets added.
>
> Could someone help me out?
>
> Thanks!
Don't touch the return key them
I just tested it on Dw CS3 - brand new page - created new
table, and
entered text.
No <p> tags -
but if you hit return key - it put in a new paragraph - as
one might
expect
~Malcolm~*...
~* -
When I click Live View, I can see my page, and it shows up in a browser just fine, but I can't edit in that mode. However, when I click Live View again, I just get a gray, blank page with the tag, meta, sytle, script, and link icons at the top left. I've been tinkering with it for the last two hours, and nothing I try is getting the page to appear in Design, or Split view. It's driving me nuts. Any suggestions?
Here's the code.
<!--
body
/* ~~ Element/tag selectors ~~ */
ul, ol, dl { /* Due to variations between browsers, it's best practices to zero padding and margin on lists. For consistency, you can either specify the amounts you want here, or on the list items (LI, DT, DD) they contain. Remember that what you do here will cascade to the .nav list unless you write a more specific selector. */
padding: 0;
margin: 0;
h1, h2, h3, h4, h5, h6, p {
margin-top: 0; /* removing the top margin gets around an issue where margins can escape from their containing div. The remaining bottom margin will hold it away from any elements that follow. */
padding-right: 15px;
padding-left: 15px; /* adding the padding to the sides of the elements within the divs, instead of the divs themselves, gets rid of any box model math. A nested div with side padding can also be used as an alternate method. */
a img { /* this selector removes the default blue border displayed in some browsers around an image when it is surrounded by a link */
border: none;
max-width: 900px;
/* ~~ Styling for your site's links must remain in this order - including the group of selectors that create the hover effect. ~~ */
a:link
a:visited
a:hover, a:active, a:focus { /* this group of selectors will give a keyboard navigator the same hover experience as the person using a mouse. */
text-decoration: none;
/* ~~ this container surrounds all other divs giving them their percentage-based width ~~ */
.container
/* ~the header is not given a width. It will extend the full width of your layout. It contains an image placeholder that should be replaced with your own linked logo~ */
.header {
background-color: #424661;
/* ~~ This is the layout information. ~~
1) Padding is only placed on the top and/or bottom of the div. The elements within this div have padding on their sides. This saves you from any "box model math". Keep in mind, if you add any side padding or border to the div itself, it will be added to the width you define to create the total width. You may also choose to remove the padding on the element in the div and place a second div within it with no width and the padding necessary for your design.
.content
/* ~~ This grouped selector gives the lists in the .content area space ~~ */
.content ul, .content ol
/* ~~ The footer ~~ */
.footer
/* ~~ miscellaneous float/clear classes ~~ */
.fltrt { /* this class can be used to float an element right in your page. The floated element must precede the element it should be next to on the page. */
float: right;
margin-left: 8px;
.fltlft { /* this class can be used to float an element left in your page. The floated element must precede the element it should be next to on the page. */
float: left;
margin-right: 8px;
.clearfloat { /* this class can be placed on a
or empty div as the final element following the last floated div (within the #container) if the #footer is removed or taken out of the #container */
clear:both;
height:0;
font-size: 1px;
line-height: 0px;
-->
!Banner.gif|height=185|alt=banner|width=960|src=Banner.gif!
Buyers
[Item 2.1 | #]
[Item 2.2 | #]
[Item 2.3 | #]
Sellers
[Item 3.1 | #]
[Item 3.1.1 | #]
[Item 3.1.2 | #]
[Item 3.2 | #]
[Item 3.3 | #]
Contact Us
About Us
Ford's Blog
Job Opportunities
Instructions
Be aware that the CSS for these layouts is heavily commented. If you do most of your work in Design view, have a peek at the code to get tips on working with the CSS for the liquid layouts. You can remove these comments before you launch your site. To learn more about the techniques used in these CSS Layouts, read this article at Adobe's Developer Center - http://www.adobe.com/go/adc_css_layouts .</p>
Layout
Since this is a one-column layout, the .content is not floated.
Logo Replacement
An image placeholder was used in this layout in the .header where you'll likely want to place a logo. It is recommended that you remove the placeholder and replace it with your own linked logo.
Be aware that if you use the Property inspector to navigate to your logo image using the SRC field (instead of removing and replacing the placeholder), you should remove the inline background and display properties. These inline styles are only used to make the logo placeholder show up in browsers for demonstration purposes.
To remove the inline styles, make sure your CSS Styles panel is set to Current. Select the image, and in the Properties pane of the CSS Styles panel, right click and delete the display and background properties. (Of course, you can always go directly into the code and delete the inline styles from the image or placeholder there.)
Footer
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", );
</script>
</body>
</html -
Rearanging of my codes when moving from code view to design view
I was wondering if there is a setting in Dreamweaver CC that can maintain the way I wrote my codes?
This is what happening:
I work in code view and write my codes. then I go check it out in design view, then I come back to my codes and Dreamweaver justify my codes... it's really annoying. is there a way to preserve the design (the way I wrote my codes and it will stay as is no matter what)
Side note: I am not talking about split view where it is expected that the code would move around with fluidity. I am talking about full code view. thanksNo I don't mean that... but I think I figured it out.
Here is what I think: Working in design fluid grid layout causes additional codes to be added to my existing codes. I have learned to start keeping a close eye on this because the names of my classes are starting to grow like crazy. I had tried to design something in fluid grid when I first got Dreamweaver (well because, that was one of a major selling point for me) I soon realized that having little exprience in css to start with tripled how complicated it became to apply proper styling throughout a webpage so I went back to the basics and learned how to work with css first. I am getting pretty good at it now and felt it was time to give Fuid grid another shot. I had forgotten about how tricky it is to keep things tight in that environment. So all it was; I am almost 99.9% sure of it was because when I went and changed some setting in the gui I didn't noticed that it tagged another name to my already name class. So in a sense I am getting multiple classes tags for one item. After a while the extra code inserted by Dreamweaver messes up all the code layout (that I have beed trying to keep tidy as much as I can) lol. Gosh! I am really starting to like Dreamweaver, but man O' man... I think I am really starting to hate using the graphical environment and starting to really understand what the old boys keeps on saying that it is best to hard code than trying to adjust things with the graphical environment. -
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. -
Form element doesn't match design view
I just tried the new forms in Muse.
After styling and moving the formfields around they don't stay where I put them in design view.
See attached images from
designview, preview and after publishing (to BC) in Chrome. (IE9 looks the same)Hi ePocket,
It looks like you've found a bug that we missed, I've added it to our database.
It seems to be caused by the use of a System Font in the submit button. To get around this, use a font that is not in the System font category.
Sorry for the inconvenience -
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.
PaulThanks 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 no longer displaying included files properly or at all
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 files at all. On the test server design view is recognizing the html from the includes but not any images or files with a "/" as the first character in the path.
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. Perhaps I should try to uninstall/reinstall Dreamweaver. Any help would be greatly appreciated. Thank you.
PaulPlease show us the code from a sample parent page and an included page.
-
Design view in Dreamweaver CC (update Oct. 2014)
Design view in Dreamweaver CC (update Oct. 2014) shows renders fonts and elements as huge making it impossible to work in that view. In live view it goes down to normal. And is there a way to switch of the blue tag inspector wrapping around the elements in focus? It's driving me nuts!
What am I doing wrong, or is there a setting I'm unaware of?Jon Fritz II wrote:
I have a sneaking suspicion that the "fix" is going to be the complete removal of Design View and a much more robust implementation of a Live View editor. I don't have anything to back that up, it's just the vibe I get from the direction DW seems to be taking.
If there is a single web design/editor/developer application that even comes close to the features and power of Dreamweaver, I have yet to find it. And I test everyone I come across. Dw truly is the last great web design powerhouse. One of the main features that makes it so powerful, is its rich WYSIWYG editor for producing and managing large sites with tons of content - otherwise known as the inappropriately named Design View.
As design surfaces go, apps like Macaw, Webflow, and Reflow nailed it. They're brilliant when it comes to prototyping designs and building & styling structures. Dreamweaver just can't compete with those types of visual workflows. Live View is barely a design surface at all, and its workflows are preposterous. That may change over time. Live View might be useful someday for prototyping designs and building & styling structures, but I would be very surprised if Live View's design surface ever... ever... ever becomes a useful content production and management surface.
If Adobe allows - or forces - the Dw team to remove Design View, leaving us without a decent WYSIWYG editor, then where does that leave web designers like myself who produce and manage corporate sites with lots of content? - It's a rhetorical question. -
I just installed CS3 and in design mode it is not showing any
CSS styling. I have to go to a web browser to see it. How can I
fix?Durangokids wrote:
> I just installed CS3 and in design mode it is not
showing any CSS styling. I have to go to a web browser to see it.
How can I fix?
1) select View>Toolbars>Style Rendering
is the first icon enabled? That will display screen media
styles. Other
icons display other media styles and/or toggle off the
rendering of
styles in design view altogether. It's easy to forget about
this toggle!
Hope that's all it is. The other possibility is that you are
using a
webroot relative path structure but your site structure isn't
the same
as the remote server.
I bet it's the first, though. Like working on your car, look
for the
easiest & cheapest solution to test first.
HTH
Donna -
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. -
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
Maybe you are looking for
-
Issue in wrapping of text in TextEdit control
Hi, I'm developing an occasionally connected application using NetWeaver Mobile 7.1. In one of the view, I use TextEdit control to display the address information where the address is a multiline text data. During testing of the application in the si
-
Firefox 3.6 or 4.0 will not install
Greetings, I am unable to install either 3.6 or 4.0 After downloading 4.0, and turning off my virus protection and closing all programs... I then begin installation in Administrator mode and during setup I am presented with this message: '''Your comp
-
How long does it take to get a line installed and ...
hey peeps just wondering if anyone else has hasd the same problems that i have experienced with bt i ordered bt infinity and bt landline mid feb and it has over a month to get a phone line which ican only dial out on and no internet it took 3 weeks t
-
Lost 30-40 gigs of files and settings
Today I suddenly lost a lot of files on my MacBook Pro 5,1. Examples of what I have lost: Files: All files on desktop exept one. No folders lost All files in the default images folder. No folders lost Settings lost: Dock is back to default No image a
-
Internet suddenly very slow... Can anyone see a pr...
ADSL line status Connection information Line state Connected Connection time 0 days, 0:09:15 Downstream 5,792 Kbps Upstream 448 Kbps ADSL settings VPI/VCI 0/38 Type PPPoA Modulation ITU-T G.992.1 Latency type Interleaved Noise margin (Down/Up) 5.9 dB