Frontpage & Netscape? :(

T

Thomas A. McKean

I am sure

This has come up before? How do I get my Frontpage sites to be compaticble
with Netscape? The text is all off in Netscape but perfect on IE.

I went into the PAGE OPTIONS and reset it for both browsers and did a SAVE, do
I need to rebuild this page again from scratch to get it to be compatible with
both? ACK!

Thomas <><
(e-mail address removed)
http://www.thomasamckean.com
Colonel, HOKC
Member, ASA, Board of Directors, 1992-1994, 1997-2000
Author, Soon Will Come the Light: A View From Inside the Autism Puzzle
Author, Light On the Horizon: A Deeper View From Inside the Autism Puzzle
 
T

Thomas A. McKean

URL for the published site?

Well I guess it isn't a secret... :) I am wrting a site (or TRYING to) for
JoAnn McFatter so she can sell her CDs online. At least that was the idea. I
was building it on my own site before we moved it to hers. So the temporary
URL is:

http://joann.thomasamckean.com

And the problem I am having is here:

http://joann.thomasamckean.com/music.htm

As you can see, the formatting is spot on with IE but way off with Netscape.

The CD cover graphics seem to be fine. It is the text that is the problem.
Almost like Netscape has a problem with layers? How do I format the text
correctly without layers? ARGH!!!!

Thomas <><
(e-mail address removed)
http://www.thomasamckean.com
Colonel, HOKC
Member, ASA, Board of Directors, 1992-1994, 1997-2000
Author, Soon Will Come the Light: A View From Inside the Autism Puzzle
Author, Light On the Horizon: A Deeper View From Inside the Autism Puzzle
 
M

Murray

Most likely there are multiple problems here -

1. You have used 'layers' on the page, and you have placed them into table
cells. This is a very common error among those not so familiar with
positioned content, and it causes lots of grief. The solution would be to
find every occurrence of such a thing on your page, e.g.,

<td width="100%" valign="top">
<div style="position: absolute; width: 828px; height: 21px; z-index:
2; left: 162px; top: 114px" id="layer4" align="left">

(note that the positioned div tag that is "layer4" is inside a <td>)

then cut that entire layer from the code of the page, and paste it back in
either just below <body> or just above </body>. Do this for each layer on
the page. That will solve that problem (by the way, align="left" is the
default alignment, and therefore redundant).

2. You have used the <p> tag and the <h1> tag as a layout tool -

<td width="15" valign="bottom">&nbsp;<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
[snip lots of them}
<p>&nbsp;</p>
<p><img src="images/clear_dot.gif"

or -

<b><font face="Arial">Music available by JoAnn McFatter.&nbsp; Click on
CD to purchase.&nbsp; Click on titles to hear samples.</font></b></div>
<h1 class="yellowheadline">&nbsp;</h1>
<h1 class="yellowheadline">&nbsp;</h1>
[snip lots of them}
<h1 class="yellowheadline">&nbsp;</h1>
<div style="position: absolute; width: 829px; height: 1644px; z-index: 1;
left: 162px; top: 147px" id="layer1">

Now, since both of these tags will respond to the browser's font display
size, by using them this way, you have guaranteed that your layout will fall
apart when someone resized their font (I suspect that this may also be
causing you some cross-browser problems). The solution is not to use any
character or resizable element as a layout or positioning device. If you
need something to be placed on the page in a certain location, you need to
make your table structure put it there, or use CSS to put it there.

3. You have nested inline layers -

<div style="position: absolute; width: 829px; height: 1644px; z-index: 1;
left: 162px; top: 147px" id="layer1">
<div style="position: absolute; width: 144px; height: 18px; z-index: 14;
left: 0px; top: 1374px" id="layer18">

and I suspect that this is also causing you problems cross-browser. If you
are going to nest layers, the inner ones need to be fully qualified CSS
layers, like this -

<div style="...." id="layer1">
<div id="layer18">blah blah</div>
</div>

assuming your stylesheet has this -

#layer18 { position: absolute; width: 144px; height: 18px; z-index: 14;
left: 0px; top: 1374px; }

Try fixing those things, and see what happens.
 
T

Thomas A. McKean

Most likely there are multiple problems here -

ACK!!!
1. You have used 'layers' on the page, and you have placed them into table
cells. This is a very common error among those not so familiar with
positioned content, and it causes lots of grief.

No, FRONTPAGE placed them into table cells. All I did was WYSIWYG.
The solution would be to
find every occurrence of such a thing on your page, e.g.,

<td width="100%" valign="top">
<div style="position: absolute; width: 828px; height: 21px; z-index:
2; left: 162px; top: 114px" id="layer4" align="left">

(note that the positioned div tag that is "layer4" is inside a <td>)

then cut that entire layer from the code of the page, and paste it back in
either just below or just above .

Okay forgive me sounding like an idiot here, but place them just above or just
bekow...what exactly?

I do have expertise, surely it is not in web site design. But I am trying to
learn!

Could yew maybe provide me an example so I know what yew mean? *Blink*

Web site is here:

http://joann.thomasamckean.com/music.htm
2. You have used the
tag and the

tag as a layout tool -
[snip lots of them}

The said:
Now, since both of these tags will respond to the browser's font display
size, by using them this way, you have guaranteed that your layout will fall
apart when someone resized their font (I suspect that this may also be
causing you some cross-browser problems).

ARGH! What tag and what tag? :(
The solution is not to use any
character or resizable element as a layout or positioning device. If you
need something to be placed on the page in a certain location, you need to
make your table structure put it there, or use CSS to put it there.

Does this mean if I want the page to be netscape compatible that I can't use
layers? :(
3. You have nested inline layers -

<div style="position: absolute; width: 829px; height: 1644px; z-index: 1;
left: 162px; top: 147px" id="layer1">
<div style="position: absolute; width: 144px; height: 18px; z-index: 14;
left: 0px; top: 1374px" id="layer18">

and I suspect that this is also causing you problems cross-browser. If you
are going to nest layers, the inner ones need to be fully qualified CSS
layers, like this -

<div style="...." id="layer1">
<div id="layer18">blah blah</div>
</div>

Okay THAT one I understand.... I fixed it and there was no difference. :(

This is very frustrating. :(

Thomas <><
(e-mail address removed)
http://www.thomasamckean.com
Colonel, HOKC
Member, ASA, Board of Directors, 1992-1994, 1997-2000
Author, Soon Will Come the Light: A View From Inside the Autism Puzzle
Author, Light On the Horizon: A Deeper View From Inside the Autism Puzzle
 
M

Murray

No, FRONTPAGE placed them into table cells. All I did was WYSIWYG.

It's the same. FP does what you tell it to. You should not tell it to do
that.
Okay forgive me sounding like an idiot here, but place them just above or
just
bekow...what exactly?

Sorry - looks like my post was munged - just above the closing body tag or
just below the opening body tag.
ARGH! What tag and what tag? :(

Does this mean if I want the page to be netscape compatible that I can't
use
layers? :(

Not at all. It means that you should not position things by inserting lots
of spaces to push it over, or lots of returns to push it down.

That should get you going.

--
Murray

Thomas A. McKean said:
Most likely there are multiple problems here -
ACK!!!

1. You have used 'layers' on the page, and you have placed them into
table
cells. This is a very common error among those not so familiar with
positioned content, and it causes lots of grief.

No, FRONTPAGE placed them into table cells. All I did was WYSIWYG.
The solution would be to
find every occurrence of such a thing on your page, e.g.,

<td width="100%" valign="top">
<div style="position: absolute; width: 828px; height: 21px; z-index:
2; left: 162px; top: 114px" id="layer4" align="left">

(note that the positioned div tag that is "layer4" is inside a <td>)

then cut that entire layer from the code of the page, and paste it back in
either just below or just above .

Okay forgive me sounding like an idiot here, but place them just above or
just
bekow...what exactly?

I do have expertise, surely it is not in web site design. But I am trying
to
learn!

Could yew maybe provide me an example so I know what yew mean? *Blink*

Web site is here:

http://joann.thomasamckean.com/music.htm
2. You have used the
tag and the

tag as a layout tool -
[snip lots of them}

The said:
Now, since both of these tags will respond to the browser's font display
size, by using them this way, you have guaranteed that your layout will
fall
apart when someone resized their font (I suspect that this may also be
causing you some cross-browser problems).

ARGH! What tag and what tag? :(
The solution is not to use any
character or resizable element as a layout or positioning device. If you
need something to be placed on the page in a certain location, you need to
make your table structure put it there, or use CSS to put it there.

Does this mean if I want the page to be netscape compatible that I can't
use
layers? :(
3. You have nested inline layers -

<div style="position: absolute; width: 829px; height: 1644px; z-index:
1;
left: 162px; top: 147px" id="layer1">
<div style="position: absolute; width: 144px; height: 18px; z-index:
14;
left: 0px; top: 1374px" id="layer18">

and I suspect that this is also causing you problems cross-browser. If
you
are going to nest layers, the inner ones need to be fully qualified CSS
layers, like this -

<div style="...." id="layer1">
<div id="layer18">blah blah</div>
</div>

Okay THAT one I understand.... I fixed it and there was no difference.
:(

This is very frustrating. :(

Thomas <><
(e-mail address removed)
http://www.thomasamckean.com
Colonel, HOKC
Member, ASA, Board of Directors, 1992-1994, 1997-2000
Author, Soon Will Come the Light: A View From Inside the Autism Puzzle
Author, Light On the Horizon: A Deeper View From Inside the Autism Puzzle
 
T

Thomas A. McKean

Sorry - looks like my post was munged - just above the closing body tag or
just below the opening body tag.

Yeah right that just messed it up even more! :(

Maybe it is time I gave up on this. Anyone wanna buy Frontpage?

Angry Thomas
 
T

Tom Pepper Willett

Sorry, I don't need to buy FP. I have FP 2003. And, FP 1.1, FP 95, FP 97,
FP 2000, FP 2002 and FP 2003 have worked great for me for years and years.

Guess I must have been doing something right? ;-)

--
===
Tom "Pepper" Willett
Microsoft MVP - FrontPage
---
About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
FrontPage 2003 Product Information:
http://www.microsoft.com/office/frontpage/prodinfo/default.mspx
Understanding FrontPage:
http://msdn.microsoft.com/office/understanding/frontpage/
===
| >Sorry - looks like my post was munged - just above the closing body tag
or
| >just below the opening body tag.
|
| Yeah right that just messed it up even more! :(
|
| Maybe it is time I gave up on this. Anyone wanna buy Frontpage?
|
| Angry Thomas
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top