another boring IE and NS/Mozilla compatibility NOT issue (Full Version)

All Forums >> [Web Development] >> Cascading Style Sheets



Message


bdaul -> another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 3:22:57)

I never thought AOL would become a bigger pain than MS...but it is.

I have a page: http://www.human-landscaping.com/PA/testing.html

that looks fine under IE. I use GoLive CS to produce it...applied the famous Netscape Fix...which seems to have done nothing. I have run the code against the CL sytax checker and the only problems have to do with unexpected "li" items.

Can someone give me a hint as to what to do next to try and produce a Mozilla/NN viewable page?

DO ANY OF YOU have recommendations on a process of designing pages using CSS that will easily look SIMILAR under both browsers?

Thanks, --bill




Giomanach -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 3:42:52)

All I can see is that you have two unordered lists <ul> opening twice.

I'll take a closer look when I get home, I have Go-Live CS there.

Dan




d a v e -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 4:00:54)

first step is validate your code - both html and css
http://validator.w3.org/ (html)
and http://jigsaw.w3.org/css-validator/ (css!)

then at least it should display ok in both, though not necessarily the exactly the same.




bdaul -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 4:27:59)

David,

Thanks...I am working through the Validator...here are some of the entries that have something to do with the Netscape Fix (in GoLive). I don't know enough to say anything definitive but...I think the lines here are what worked in other files? Any comments on the following:

#

Line 46, column 21: there is no attribute "NAME"

<csactionitem name="6886CF20"></csactionitem>

You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute.


#

Line 46, column 31: element "CSACTIONITEM" undefined

<csactionitem name="6886CF20"></csactionitem>

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).


#

Line 47, column 22: "IMPORT" is not a member of a group specified for any attribute

<csscriptdict import>


#

Line 47, column 22: element "CSSCRIPTDICT" undefined

<csscriptdict import>

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).


#

Line 50, column 15: element "CSACTIONDICT" undefined

<csactiondict>

You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element), or by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).




bdaul -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 6:05:02)

I am reading through docs...is there anything wrong with the following:

<style type="text/css">

div#quest {font-size: 11pt; font-family: "Times New Roman", Times, serif;}
</style>

...
...

<DIV id=quo>"Right here...in the heart of Palo Alto"</DIV>
...
...

===============================
I am trying to figure out my validation errors




Giomanach -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 6:12:23)

<style type="text/css">
.quest {
  font-size: 11pt;
  font-family: "Times New Roman", Times, serif;
}
</style>

<div class="quo">"Right here...in the heart of Palo Alto"</div>

I've just changed it to my prefered layout of cosing, you don't have to keep it this way, I've also altered is stlighty for you.

Dan




bdaul -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 6:13:33)

One perhaps getting close to last thing...I can't figure out what the context error is on these two objects:

* Line: 11 Context : hr

Parse Error - hr.1 {position: absolute; left: 50px; top: 135px; border: 0; width: 734px; color: #993300; height: 20px; z-index: 1;}

* Line: 11 Context : hr

Parse Error - hr.2 {border: 0; color: #993300; height: 2px;}

THANKS




Giomanach -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 6:20:26)

hr = Horizontal Rule, Example:




You can't set a position for it.

hr.1 {
position: absolute;
left: 50px;
top: 135px;
border: 0;
width: 734px;
color: #993300;
height: 20px;
z-index: 1;
}

If the above is for something other than a Horizontal rule, you will need to identify it as a class or id:

.hr.1

-or-

#hr.1

I would go with .hr.1




bdaul -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 6:43:49)

hmmm....interesting...under IE I actually can position it...but not NN...thanks...




d a v e -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 7:17:43)

re: font size pt (points) are print only. use percentages, ems, relatives font size such as smaller, etc, or pixels if you make sure they can be resized in IE.




c1sissy -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 8:21:54)

quote:

ORIGINAL: Giomanach

<style type="text/css">
.quest {
   font-size: 11pt;
   font-family: "Times New Roman", Times, serif;
}
</style>

<div class="quo">"Right here...in the heart of Palo Alto"</div>

I've just changed it to my prefered layout of cosing, you don't have to keep it this way, I've also altered is stlighty for you.

Dan

If you read the css2 specs, (I know boring, and time consuming, and part of the class I'm behind on right now) all your code example, <div class="quo"> need quotes in your html/xhtml coding.

Make sure you validate your html first, then go and valadate the css. Sometimes if you have something small off in the begining it will throw your whole document off. Fix each item in the order that the valadator is giving it to you.


HERE is a link for styling the hr. Gives information on NS and on IE.




d a v e -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 11:14:04)

that's a useful link - i was using this before
hr {
 height: 0px;
	border-style: solid;
	border-width: 1px 0 0 0;
	border-color: #0088cc;
}


which is fine if you want a 1px hr but not if you want more than 1px (guess which pile of pants doesn't do it... )




Giomanach -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 11:15:52)

Can't be IE....that does everything...the wrong way![:D]

I've never really played with the <hr> element properties....alwyas let them grey..as that's what suited the site best

Dan




d a v e -> RE: another boring IE and NS/Mozilla compatibility NOT issue (9/6/2004 11:18:09)

oh yeah Bill you have a missing word from first page left column
quote:

It's very easy to do: simply a local cause from the list to the right and give them some time on Saturday, September 11.


simply (choose?/select/pick?) a local cause...




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.0625