Frames overlapping in some browsers

[StrictlyBallroom]

My web site www.ceroclondon.com appears fine in internet explorer, however in
some other browsers like 'FireFox' the target frame boxes are all
over-lapping.

I have started using target frames as I like the idea of having boxes of
information side by side rather than one long list which is the default way
that FrontPage seems to want to work.

 

[Rob Giordano \(Crash\)]

Frames? I don't see any use of frames on this site.


message | My web site www.ceroclondon.com appears fine in internet explorer, however
in
| some other browsers like 'FireFox' the target frame boxes are all
| over-lapping.
|
| I have started using target frames as I like the idea of having boxes of
| information side by side rather than one long list which is the default
way
| that FrontPage seems to want to work.

 

[StrictlyBallroom]

Rob,

I think I was using wrong terminology, I have used 'layers' on my site and
they are overlapping,
Mike

 

[Rob Giordano \(Crash\)]

absolute positioning is what causes that. one of the mvp's posted a really
great explanation of absolute and relative positioning...only I forgot where
the post is located - it was recent. you may want to search this ng.



message | Rob,
|
| I think I was using wrong terminology, I have used 'layers' on my site and
| they are overlapping,
| Mike
|
| "Rob Giordano (Crash)" wrote:
|
| > Frames? I don't see any use of frames on this site.
| >
| >
| > message | > | My web site www.ceroclondon.com appears fine in internet explorer,
however
| > in
| > | some other browsers like 'FireFox' the target frame boxes are all
| > | over-lapping.
| > |
| > | I have started using target frames as I like the idea of having boxes
of
| > | information side by side rather than one long list which is the
default
| > way
| > | that FrontPage seems to want to work.
| >
| >
| >

 

[Ronx]

Probably posted by Murray.
See http://www.great-web-sights.com/g_layerlaws.asp and
http://www.great-web-sights.com/g_layersdemo.asp


One problem with absolutely positioned layers, not mentioned on this page,
is what happens when the font-size changes. Different browsers will render
the samee font in different ways (depending on how you define the
font-size), so there is no absolute size for the content of a layer - hence
absolute positioning will fail unless you build in sufficient redundant
space for fonts to grow and shrink. Not to mention the *users* changing the
font size for comfortable reading....

You can use <divs> for page layout - some say you should - but IMO use
relative positioning, and the CSS float attribute to bring <divs> side by
side.