By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,320 Members | 2,109 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,320 IT Pros & Developers. It's quick & easy.

IE Looks fine, Mozilla looks garbled, Positioning Help please

P: n/a
Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
completely CSS positioned page, and was wondering if any resident CSS guru
might quickly be able to find the problem(s). Thank you.

In IE, the page looks how I want it to look (picture below):
www.sunbadgeco.com/sunmetal/ie.jpg

In Mozilla Firefox, somehow it's not quite right (pic below):
www.sunbadgeco.com/sunmetal/mozillafirefox.jpg

Here is the CSS and HTML (with some omissions for brevity):

body {
background-image: url(../images/bg.jpg);
border: 4px inset #454545;
width: 636px;
margin: 20px auto;
text-align: center;
}
#container {
background-color: #000000;
color: #AEAA9D;
font-family: Trebuchet MS, Tahoma, Arial, "Times New Roman", sans-serif;
font-size: 100%;
padding: 0;
margin: 0;
text-align: left;
}
#mainart {
display: block;
margin-left: auto;
margin-right: auto;
margin-top: 55px;
margin-bottom: 35px;
text-align: center;
}
..artblock {
width: 450px;
border: 4px outset #AEAA9D;
color: #F8F4E5;
background-color: #857F75;
}
..artistname {
float: left;
padding: 10px;
top: 80px;
text-align: left;
}
..artistfirst {
color: #F8F4E5;
font-size: 150%;
font-weight: bold;
}
..limitededition {
font-size: 70%;
}
..artimage {
float: right;
font-size: 1px;
border: 4px inset #AEAA9D;
text-align: center;
}
#footer {
font-size: 70%;
text-align: center;
}
..hrgraphic {
font-size: 1px;
}
#navfooter {
display: block;
margin-top: 2px;
margin-bottom: 5px;
}
<body>
<div id="container">

<div id="mainart">
<div class="artblock">
<div class="artistname">
<span class="artistfirst">S</span>teven <span
class="artistfirst">H</span>ofberger<br /><span
class="limitededition">Limited Editions: 50</span>
</div>
<div class="artimage">
<img src="images/hofberger_minivase.jpg" height="200" width="200" alt=""
/>
</div>
</div>
</div>

<div id="footer">
<div class="hrgraphic">
<img src="images/bottomlights.jpg" width="246" height="52" alt="" /><br />
<img src="images/hr.jpg" width="580" height="1" alt="" />
</div>

<div id="navfooter">
<a href="artists.htm" class="navfooter">Artists</a>|<a href="contact.htm"
class="navfooter">Contact Information</a>|<a href="about.htm"
class="navfooter">About Us</a>
</div>

<div id="copyright">
Copyright ©2004 Sunmetal Fine Art Co. All Rights Reserved.
</div>
</div>

</div>
Jul 20 '05 #1
Share this Question
Share on Google+
21 Replies


P: n/a
On Sun, 13 Jun 2004 19:04:19 GMT, Applebrownbetty
<applebrown@deletethisspace_gamebanshee.com> wrote:
Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
completely CSS positioned page, and was wondering if any resident CSS
guru
might quickly be able to find the problem(s). Thank you.

In IE, the page looks how I want it to look (picture below):
www.sunbadgeco.com/sunmetal/ie.jpg

In Mozilla Firefox, somehow it's not quite right (pic below):
www.sunbadgeco.com/sunmetal/mozillafirefox.jpg

Here is the CSS and HTML (with some omissions for brevity):


Screenshots and incomplete code are not sufficient. One omission - whether
you used a doctype properly or not - might be critical. Please, instead of
snipped code, upload an example showing the problem and give us the URL.
Jul 20 '05 #2

P: n/a
"Neal" <ne*****@yahoo.com> wrote in message
news:op**************@news.individual.net...
On Sun, 13 Jun 2004 19:04:19 GMT, Applebrownbetty
<applebrown@deletethisspace_gamebanshee.com> wrote:
Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
completely CSS positioned page, and was wondering if any resident CSS
guru
might quickly be able to find the problem(s). Thank you.

In IE, the page looks how I want it to look (picture below):
www.sunbadgeco.com/sunmetal/ie.jpg

In Mozilla Firefox, somehow it's not quite right (pic below):
www.sunbadgeco.com/sunmetal/mozillafirefox.jpg

Here is the CSS and HTML (with some omissions for brevity):


Screenshots and incomplete code are not sufficient. One omission - whether
you used a doctype properly or not - might be critical. Please, instead of
snipped code, upload an example showing the problem and give us the URL.


That is near complete code Neal and near complete CSS. The only things I
left out are the navbar information which work perfectly on both pages. Here
is the complete HTML but you'll find it just about the same. The logo,
navbar and footer sections work on both IE and Mozilla, it's just the
mainart class to the footer that's causing the problem:

Here's a link to the main page of the site. It's exactly the same without
the new CSS, except for the middle mainart class that I changed on the
artists page: www.sunbadgeco.com/sunmetal/index.htm

This is the relavant HTML of the page in discussion however. As you can see
I only cut out the navbar stuff.

<link href="css/sunstyle.css" rel="stylesheet" type="text/css" />
</head>

<body>
<div id="container">

<div id="logo">
<a href="/sunmetalfineart/"><img src="images/logo.jpg" width="450"
height="120" border="0" alt="Sunmetal Fine Art Co. Home" /></a>
</div>

<div id="navmain">
<div>
<img src="images/navbar.jpg" alt="" />
</div>

<a href="artists.htm" id="artists"><img src="images/artists_active.jpg"
class="pload" border="0" width="148" height="35" alt="" /><img
src="images/pixel.gif" border="0" width="148" height="35" alt="Featured
Artists" /></a><img src="images/diamond.gif" width="55" height="35" alt=""
/><a href="contact.htm" id="contact"><img src="images/contact_active.jpg"
class="pload" border="0" width="163" height="35" alt="" /><img
src="images/pixel.gif" border="0" width="163" height="35" alt="Contact
Information" /></a><img src="images/diamond.gif" width="55" height="35"
alt="" /><a href="about.htm" id="about"><img src="images/about_active.jpg"
class="pload" border="0" width="90" height="35" alt="" /><img
src="images/pixel.gif" border="0" width="90" height="35" alt="About Us"
/></a>

<div>
<img src="images/navbar.jpg" alt="" />
</div>
</div>

<div id="mainart">
<div class="artblock">
<div class="artistname">
<span class="artistfirst">S</span>teven <span
class="artistfirst">H</span>ofberger<br /><span
class="limitededition">Limited Editions: 50</span>
</div>
<div class="artimage">
<img src="images/hofberger_minivase.jpg" height="200" width="200" alt=""
/>
</div>
</div>
</div>

<div id="footer">
<div class="hrgraphic">
<img src="images/bottomlights.jpg" width="246" height="52" alt="" /><br />
<img src="images/hr.jpg" width="580" height="1" alt="" />
</div>

<div id="navfooter">
<a href="artists.htm" class="navfooter">Artists</a>|<a href="contact.htm"
class="navfooter">Contact Information</a>|<a href="about.htm"
class="navfooter">About Us</a>
</div>

<div id="copyright">
Copyright ©2004 Sunmetal Fine Art Co. All Rights Reserved.
</div>
</div>

</div>
</body>
</html>

Jul 20 '05 #3

P: n/a
Applebrownbetty wrote:
Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
completely CSS positioned page, and was wondering if any resident CSS guru
might quickly be able to find the problem(s). Thank you.

In IE, the page looks how I want it to look (picture below):
www.sunbadgeco.com/sunmetal/ie.jpg

In Mozilla Firefox, somehow it's not quite right (pic below):
www.sunbadgeco.com/sunmetal/mozillafirefox.jpg


First, you should cite Web addresses as URLs (not just hostnames with a path
slapped on the end). Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your server,
as opposed to slopping it on the end of your Usenet article.

--
Shawn K. Quinn
Jul 20 '05 #4

P: n/a
"Shawn K. Quinn" <sk*****@xevious.kicks-ass.net> wrote in message
news:O_********************@speakeasy.net...
Applebrownbetty wrote:
Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
completely CSS positioned page, and was wondering if any resident CSS guru might quickly be able to find the problem(s). Thank you.

In IE, the page looks how I want it to look (picture below):
www.sunbadgeco.com/sunmetal/ie.jpg

In Mozilla Firefox, somehow it's not quite right (pic below):
www.sunbadgeco.com/sunmetal/mozillafirefox.jpg
First, you should cite Web addresses as URLs (not just hostnames with a

path slapped on the end).
Why?
Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your server,
as opposed to slopping it on the end of your Usenet article.


And why is that? It seemed easy enough to read to me (not sloppy as you
suggested) and it would look hardly different if you chose "view source"
from the actual page.
Jul 20 '05 #5

P: n/a
DU
Applebrownbetty wrote:
"Neal" <ne*****@yahoo.com> wrote in message
news:op**************@news.individual.net...
On Sun, 13 Jun 2004 19:04:19 GMT, Applebrownbetty
<applebrown@deletethisspace_gamebanshee.com> wrote:

Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
completely CSS positioned page, and was wondering if any resident CSS
guru
might quickly be able to find the problem(s). Thank you.

In IE, the page looks how I want it to look (picture below):
www.sunbadgeco.com/sunmetal/ie.jpg

In Mozilla Firefox, somehow it's not quite right (pic below):
www.sunbadgeco.com/sunmetal/mozillafirefox.jpg

Here is the CSS and HTML (with some omissions for brevity):


Screenshots and incomplete code are not sufficient. One omission - whether
you used a doctype properly or not - might be critical. Please, instead of
snipped code, upload an example showing the problem and give us the URL.

That is near complete code Neal and near complete CSS.


[snipped]

You were asked to upload an example and to give an url. Neal's request
was reasonable and justified. You post code again. Maybe you need to
first understand why it is a lot better for you and your webpage to post
an url. Maybe anything else is secondary for now.

DU
Jul 20 '05 #6

P: n/a
DU
Applebrownbetty wrote:
"Shawn K. Quinn" <sk*****@xevious.kicks-ass.net> wrote in message
news:O_********************@speakeasy.net...
Applebrownbetty wrote:

Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
completely CSS positioned page, and was wondering if any resident CSS
guru
might quickly be able to find the problem(s). Thank you.

In IE, the page looks how I want it to look (picture below):
www.sunbadgeco.com/sunmetal/ie.jpg

In Mozilla Firefox, somehow it's not quite right (pic below):
www.sunbadgeco.com/sunmetal/mozillafirefox.jpg


First, you should cite Web addresses as URLs (not just hostnames with a


path
slapped on the end).

Why?

Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your server,
as opposed to slopping it on the end of your Usenet article.

And why is that? It seemed easy enough to read to me (not sloppy as you
suggested) and it would look hardly different if you chose "view source"
from the actual page.


Ok, then, post the http headers, the doctype declaration and the
content-type of your external stylesheet along with the rest of your
code. If you don't understand why these are important, then someone will
explain what you obviously don't understand here.

DU
Jul 20 '05 #7

P: n/a
"Applebrownbetty" <applebrown@deletethisspace_gamebanshee.com> writes:
"Shawn K. Quinn" <sk*****@xevious.kicks-ass.net> wrote:

First, you should cite Web addresses as URLs (not just hostnames with a

path
slapped on the end).


Why?


Fair question. Dumping hostnames with trailing path components for
decorational purposes is aesthetically satisfying.
Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your server,
as opposed to slopping it on the end of your Usenet article.


And why is that?


Right. You want to be on CSS-discuss, not Usenet.

(Supplementing info: CSS-discuss has a firm set of rules, 25% of which
are rigidly enforced; you need to lurk a while to recognise those.
Usenet, on the other hand, has no rules whatsoever; you need to lurk
considerably longer to understand them.)
HTH, HAND

--
| ) 111010111011 | http://bednarz.nl/
-(
| ) Distribute me: http://binaries.bednarz.nl/mp3/aicha
Jul 20 '05 #8

P: n/a
On Sun, 13 Jun 2004 21:48:13 GMT, Applebrownbetty
<applebrown@deletethisspace_gamebanshee.com> wrote:
"Neal" <ne*****@yahoo.com> wrote in message
news:op**************@news.individual.net...
Screenshots and incomplete code are not sufficient. One omission -
whether
you used a doctype properly or not - might be critical. Please, instead
of
snipped code, upload an example showing the problem and give us the URL.
That is near complete code Neal and near complete CSS. The only things I
left out are the navbar information which work perfectly on both pages.


But you also omitted the doctype, which I mentioned is critical in
avoiding these things.
Here's a link to the main page of the site. It's exactly the same without
the new CSS, except for the middle mainart class that I changed on the
artists page: www.sunbadgeco.com/sunmetal/index.htm
On this page I see the doctype, is it on the new page? I simply don't know
that, and it's the first thing I'd look for.
This is the relavant HTML of the page in discussion however. As you can
see
I only cut out the navbar stuff.


Ok, my very best guess, assuming the doctype is correct: your floats have
no width assigned. Try adding widths. The searchlight image appears to be
going higher because it isn't clearing the floats. Exactly what to do,
it's hard to diagnose without my investing more time into this.

What I'd like you to appreciate is this: for anyone to see the problem
actually happening, we'd have to set up your HTML in a file on our own,
plus a css file, and then view it in IE and Mozilla. Either that, or some
true genius can read the code and figure it out in their head. The latter
implies more faith in the abilities of the regulars of this newsgroup than
I think it's safe to assume; the former assumes we have the time to devote
to recreating the problem.

When you provide a URL, stripped down to the essentials which show the
problem, you demonstrate that you've put some effort toward discovering
the problem, and you demonstrate respect for the fact that we're all here
to discuss CSS, not serve as free help gurus of some sort. I'm not
insinuating you really think we're all here just to help you, but as you
definitely have a server to which you can post a test case, and you
definitely have code ready to upload, the fact that you haven't simply
done so is confusing. It so obviously makes the process of finding the
problem so much easier.

Again, *please* post a URL to a test case which exhibits the problem - and
if possible, remove anything which you can which still leaves the problem
intact.
Jul 20 '05 #9

P: n/a
> font-family: Trebuchet MS, Tahoma, Arial, "Times New Roman", sans-serif;

You need quotes around Trebuchet MS [like this: "Trebuchet MS"].
font-size: 100%;
padding: 0;
margin: 0;
text-align: left;
}
#mainart {
display: block;
margin-left: auto;
margin-right: auto;
margin-top: 55px;
margin-bottom: 35px;


Why not just use margin:55px auto 35px; ?

You're supposed to also specify widths when you're using float. I don't
know if these are the things that are making your site dodgy-looking but
keep at it.

Don't forget to specify relevant alt text for images.

HTH,

Nick.
Jul 20 '05 #10

P: n/a
Applebrownbetty wrote:
Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your server,
as opposed to slopping it on the end of your Usenet article.


And why is that? It seemed easy enough to read to me (not sloppy as you
suggested) and it would look hardly different if you chose "view source"
from the actual page.

Dude. Are you defective? You ask for help then complain when they ask
you provide your problem in a form that is easy to diagnose. Just do it.
Transcriptions into a post are guaranteed to have something missing,
misspelled, or otherwise incomplete. That is why a link to the problem is
requested.

--
jmm dash list at sohnen-moe dot com
(Remove .TRSPAMTR for email)
Jul 20 '05 #11

P: n/a
"Eric B. Bednarz" <be*****@fahr-zur-hoelle.org> wrote in message
news:m3************@email.bednarz.nl...
"Applebrownbetty" <applebrown@deletethisspace_gamebanshee.com> writes:
"Shawn K. Quinn" <sk*****@xevious.kicks-ass.net> wrote:

First, you should cite Web addresses as URLs (not just hostnames with a

path
slapped on the end).


Why?


Fair question. Dumping hostnames with trailing path components for
decorational purposes is aesthetically satisfying.


Huh? It appears to be some sort of joke, but I don't see it.
Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your server, as opposed to slopping it on the end of your Usenet article.


And why is that?


Right. You want to be on CSS-discuss, not Usenet.


What is CSS discuss? Sorry, I haven't lurked here often, though I have been
on usenet for quite some time. Just not on primarily on technical groups
where new people are berated (rather than helped) if they post reasonable
queries, yet not perfectly suited to a few regulars' style.

Jul 20 '05 #12

P: n/a
"James Moe" <jm***************@sohnen-moe.com> wrote in message
news:ca**********@216.39.176.69...
Applebrownbetty wrote:
Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your server,as opposed to slopping it on the end of your Usenet article.


And why is that? It seemed easy enough to read to me (not sloppy as you
suggested) and it would look hardly different if you chose "view source"
from the actual page.

Dude. Are you defective? You ask for help then complain when they ask
you provide your problem in a form that is easy to diagnose. Just do it.
Transcriptions into a post are guaranteed to have something missing,
misspelled, or otherwise incomplete. That is why a link to the problem is
requested.


Must Conform or be banished.

So exactly what are the problems with Copy and Paste? What I posted before
wasn't complete... missing a DOCTYPE as noted above, but there were no
errors, dude.
Jul 20 '05 #13

P: n/a
"e n | c k m a" <bo*@marley.com> wrote in message
news:lC*******************@news-server.bigpond.net.au...
font-family: Trebuchet MS, Tahoma, Arial, "Times New Roman",
sans-serif;
You need quotes around Trebuchet MS [like this: "Trebuchet MS"].
font-size: 100%;
padding: 0;
margin: 0;
text-align: left;
}
#mainart {
display: block;
margin-left: auto;
margin-right: auto;
margin-top: 55px;
margin-bottom: 35px;


Why not just use margin:55px auto 35px; ?

You're supposed to also specify widths when you're using float. I don't
know if these are the things that are making your site dodgy-looking but
keep at it.


Thanks, that might be a problem. I'll add widths and see what happens.

Jul 20 '05 #14

P: n/a
"Neal" <ne*****@yahoo.com> wrote in message
news:op**************@news.individual.net...
On Sun, 13 Jun 2004 21:48:13 GMT, Applebrownbetty
<applebrown@deletethisspace_gamebanshee.com> wrote:
"Neal" <ne*****@yahoo.com> wrote in message
news:op**************@news.individual.net...
Screenshots and incomplete code are not sufficient. One omission -
whether
you used a doctype properly or not - might be critical. Please, instead
of
snipped code, upload an example showing the problem and give us the
URL.
That is near complete code Neal and near complete CSS. The only things I
left out are the navbar information which work perfectly on both pages.
But you also omitted the doctype, which I mentioned is critical in
avoiding these things.


Sorry, forgot and did not know prior to building it that the type made a
difference with respect to the CSS. Here it is:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Here's a link to the main page of the site. It's exactly the same without the new CSS, except for the middle mainart class that I changed on the
artists page: www.sunbadgeco.com/sunmetal/index.htm


On this page I see the doctype, is it on the new page? I simply don't know
that, and it's the first thing I'd look for.
This is the relavant HTML of the page in discussion however. As you can
see
I only cut out the navbar stuff.


Ok, my very best guess, assuming the doctype is correct: your floats have
no width assigned. Try adding widths. The searchlight image appears to be
going higher because it isn't clearing the floats. Exactly what to do,
it's hard to diagnose without my investing more time into this.


Thanks, I'll start with widths, and appreciate you taking the time to
notice.
What I'd like you to appreciate is this: for anyone to see the problem
actually happening, we'd have to set up your HTML in a file on our own,
plus a css file, and then view it in IE and Mozilla. Either that, or some
true genius can read the code and figure it out in their head.
This is where I made the mistake. I did assume that CSS regulars could
simply read simple HTML and CSS and "see" it in their head if it wasn't too
complicated. I try to do that when reading C-scripting for games, but it
would have been easier after all this mess to post it to the site.
When you provide a URL, stripped down to the essentials which show the
problem, you demonstrate that you've put some effort toward discovering
the problem, and you demonstrate respect for the fact that we're all here
to discuss CSS, not serve as free help gurus of some sort. I'm not
insinuating you really think we're all here just to help you, but as you
definitely have a server to which you can post a test case, and you
definitely have code ready to upload, the fact that you haven't simply
done so is confusing. It so obviously makes the process of finding the
problem so much easier.


I appreciate your answer and if the problem is not solved, post the new code
to the server after trying the widths.
Jul 20 '05 #15

P: n/a
I posted everything to the server, and adding a width of 50%, 200px, etc.
didn't seem to help the lights or positioning in Firefox. Still looks fine
in IE. I left it as it was in the first post.

Here's the link: www.sunbadgeco.com/sunmetal/artiststest.htm

Here's the CSS: www.sunbadgeco.com/sunmetal/css/sunstyletest.css

Thanks for any help.
Jul 20 '05 #16

P: n/a
Applebrownbetty wrote:
Transcriptions into a post are guaranteed to have something missing,
misspelled, or otherwise incomplete. That is why a link to the problem is
requested.
Must Conform or be banished.

You ask for help then complain when asked to provide your problem in a
form that is easy to diagnose.
So exactly what are the problems with Copy and Paste? What I posted before
wasn't complete... missing a DOCTYPE as noted above,

Transcriptions into a post are guaranteed to have something missing,
misspelled, or otherwise incomplete. That is why a link to the problem is
requested.
--
jmm dash list at sohnen-moe dot com
(Remove .TRSPAMTR for email)
Jul 20 '05 #17

P: n/a
On Mon, 14 Jun 2004 19:44:18 GMT, Applebrownbetty
<applebrown@deletethisspace_gamebanshee.com> wrote:
I posted everything to the server, and adding a width of 50%, 200px, etc.
didn't seem to help the lights or positioning in Firefox. Still looks
fine
in IE. I left it as it was in the first post.

Here's the link: www.sunbadgeco.com/sunmetal/artiststest.htm

Here's the CSS: www.sunbadgeco.com/sunmetal/css/sunstyletest.css

Thanks for any help.

Number one - .artblock contains only floated elements, so it has no
inherit height. Add something "real" in this div after the floats, set to
clear. I added

<div class="clear">&nbsp;</div>

after the "artimage" div, the style being .clear {clear: both;}.

Number two - a few tweaks to the CSS. Check below...

#mainart {
display: block;
margin-left: auto;
margin-right: auto;
margin-top: 55px;
margin-bottom: 35px;
height: 200px;
}
..artblock {
width: 450px;
margin: auto;
border: 4px outset #AEAA9D;
color: #F8F4E5;
background-color: #857F75;
}
..artistname {
float: left;
padding: 10px;
text-align: left;
}
..artistfirst {
color: #F8F4E5;
font-size: 150%;
font-weight: bold;
}
..limitededition {
font-size: 70%;
}
..artimage {
float: right;
font-size: 1px;
border: 4px inset #AEAA9D;
text-align: center;
}
..artspace {
font-size: 1px;
height: 10px;
}
Jul 20 '05 #18

P: n/a
On Mon, 14 Jun 2004 17:32:31 GMT, Applebrownbetty
<applebrown@deletethisspace_gamebanshee.com> wrote:
But you also omitted the doctype, which I mentioned is critical in
avoiding these things.


Sorry, forgot and did not know prior to building it that the type made a
difference with respect to the CSS.


That's EXACTLY why posting a test case is preferred! :) You never know
what essential detail you never knew was part of a problem you're going to
forget. Even the way the server serves the page can cause problems the
uninitiated would never predict.
Jul 20 '05 #19

P: n/a
DU
Applebrownbetty wrote:
"James Moe" <jm***************@sohnen-moe.com> wrote in message
news:ca**********@216.39.176.69...
Applebrownbetty wrote:
Second, it's nearly impossible for those willing to
help you to actually do so unless you put the CSS and HTML on your
server,
as opposed to slopping it on the end of your Usenet article.

And why is that? It seemed easy enough to read to me (not sloppy as you
suggested) and it would look hardly different if you chose "view source"
from the actual page.

Dude. Are you defective? You ask for help then complain when they ask
you provide your problem in a form that is easy to diagnose. Just do it.
Transcriptions into a post are guaranteed to have something missing,
misspelled, or otherwise incomplete. That is why a link to the problem is
requested.

Must Conform or be banished.


No. That's not it. No one is banishing you or anything. All we're saying
is post an helpful post if you want serious help. All we're saying is be
consequent or accept consequences.
If you don't want serious help, then don't post useful, relevant info in
your post.
If you want guess work, maybes and whatever-suit-you answers, then just
post code with vague, general, abstract comments.
If you want to waste others' time, just post pointless posts. What's so
difficult to understand here?
So exactly what are the problems with Copy and Paste? What I posted before
wasn't complete... missing a DOCTYPE as noted above, but there were no
errors, dude.


Your stylesheet may not be working, you know.
"Why is my external stylesheet not working ? (...) External stylesheets
shall also be served from the www-server with a MIME-type of 'text/css'
in its 'Content Type:' HTTP header. You may need to negotiate with your
server admin to add this MIME type to your server if you are not able to
configure the server yourself." -
http://css.nu/faq/ciwas-aFAQ.html#QA05
Stylesheet authoring FAQ v1.16 from comp.webauthoring.stylesheet

"(...) a web browser has no way, according to the HTTP specification, of
knowing that the author actually intended the content to be processed
and displayed in a way different from that implied by the reported MIME
type. Some other web browsers, such as Microsoft® Internet Explorer, try
to allow for misconfigured web servers and applications by guessing what
the correct MIME type should be. This has sheltered many web
administrators from their own errors, since Internet Explorer will
continue to process content as expected even though the web server is
misconfigured, e.g. displays an image which is reported to be plain text."
http://devedge.netscape.com/viewsource/2003/mime-types/
Properly Configuring Server MIME Types from Netscape DevEdge

How in the world are readers of your post going to figure out that your
server may be misconfigured without seeing http headers, when they read
your pasted code in your posts?

DU
Jul 20 '05 #20

P: n/a
Applebrownbetty wrote:
What is CSS discuss?
An email discussion of css.
Sorry, I haven't lurked here often
You should before posting. And you should read the faq, too.
though I have been on usenet for quite some time.
In that case, you have no excuse for not lurking first, or at least
spending some time reading the archives. Any experienced usenaut knows
that.
Just not on primarily on technical groups where new people are
berated (rather than helped) if they post reasonable queries, yet
not perfectly suited to a few regulars' style.


Perhaps this will come as a shock, but very few people here will lose
sleep if you don't get your problem solved.

Many participants here will donate their expertise to help others, but
if those who want help stubbornly refuse to make it easy, the most
knowledable participants will simply move on to another post.

http://www.catb.org/~esr/faqs/smart-questions.html

--
Brian (remove ".invalid" to email me)
http://www.tsmchughs.com/
Jul 20 '05 #21

P: n/a
Applebrownbetty wrote:
"Shawn K. Quinn" <sk*****@xevious.kicks-ass.net> wrote in message
news:O_********************@speakeasy.net...
Applebrownbetty wrote:
> Hi, I've run into a problem with IE 6 vs. Mozilla when displaying a
> completely CSS positioned page, and was wondering if any resident CSS guru > might quickly be able to find the problem(s). Thank you.
>
> In IE, the page looks how I want it to look (picture below):
> www.sunbadgeco.com/sunmetal/ie.jpg
>
> In Mozilla Firefox, somehow it's not quite right (pic below):
> www.sunbadgeco.com/sunmetal/mozillafirefox.jpg


First, you should cite Web addresses as URLs (not just hostnames with a

path
slapped on the end).


Why?


So we know what protocol to use to access it, and so programs can
automagically extract the addresses without having to also extract every
occurence of www.example.com that people type in to running text. That was
the entire point of introducing URL syntax to begin with.
Second, it's nearly impossible for those willing to help you to actually
do so unless you put the CSS and HTML on your server, as opposed to
slopping it on the end of your Usenet article.


And why is that? It seemed easy enough to read to me (not sloppy as you
suggested) and it would look hardly different if you chose "view source"
from the actual page.


The served content is not always byte-for-byte equal to what you have on the
hard disk. It sounds counterintuitive, but it has happened in a few cases.

That, and I can't tell where the CSS begins and ends, and where the HTML
begins and ends.

--
Shawn K. Quinn
Jul 20 '05 #22

This discussion thread is closed

Replies have been disabled for this discussion.