Vertical Overlap

Hi All,

In a recent thread by Julie, on the subject of sitemap, Gray Owl
posted this site: http://brutontown.co.uk/_sitemap.html
When I went to his page http://brutontown.co.uk/history/bruton_history.html
on this site, I noticed something I have seen on some of my site
pages.

At the bottom of that page he has the text “Bruton in 1897”. This
looks fine in Safari, but in Firefox this text is overlapped with the
box above the text.
It looks fine in Opera, but not Camino. I am sure it looks fine in FW.

As I said, I have seen this on some of my pages. It looks fine in FW
Page and Preview modes and in some browsers but not others.

When I put the above page side by side on my screen, with Safari and
Firefox, the main problem seems to be Firefox puts more space between
the lines than Safari.
But Firefox also puts more space between the words. The combined
effect is to make the box labeled “History of Bruton Town” longer in
Firefox than Safari.
The text “Bruton in 1897” is at a fixed vertical position on the page,
not relative to the box above it.

I have generally written this off as the general problem with
different browsers doing things differently.
I then move the stuff down until there is no overlap with any browser
I have on my computer.
After the “fix”, in FW page mode it generally looks like a LOT of
vertical space between the objects.

Is this something we have to live with, or is there a method to avoid
this?

Thanks,
LLE


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Yes, this is why people put up with building inline layouts. They
don’t suffer from this problem at all, because all of the visible
elements share a common container, and thus one shoves the next out of
the way when it’s larger than originally intended.

You can also use a table layout, as they don’t suffer from this
problem at all. But there are other trade-offs inherent in that choice.

Have a read on this forum and on Dan Jasker’s many screencasts. Dan
refers to this as a “box model” layout, but that’s a misnomer.

Walter

On Jun 22, 2010, at 8:35 PM, LLE Freeway wrote:

After the “fix”, in FW page mode it generally looks like a LOT of
vertical space between the objects.

Is this something we have to live with, or is there a method to
avoid this?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks Walter.

I went to Dan Jasker’s site and discovered his buttons don’t work in
Firefox, but they seem to in Safari.
I’m not having a good evening, think I’ll give it a break.
Once again, thanks Walter for your prompt reply.

LLE

On Jun 22, 2010, at 8:43 PM, Walter Lee Davis wrote:

Yes, this is why people put up with building inline layouts. They
don’t suffer from this problem at all, because all of the visible
elements share a common container, and thus one shoves the next out of
the way when it’s larger than originally intended.

You can also use a table layout, as they don’t suffer from this
problem at all. But there are other trade-offs inherent in that choice.

Have a read on this forum and on Dan Jasker’s many screencasts. Dan
refers to this as a “box model” layout, but that’s a misnomer.

Walter

On Jun 22, 2010, at 8:35 PM, LLE Freeway wrote:

After the “fix”, in FW page mode it generally looks like a LOT of
vertical space between the objects.

Is this something we have to live with, or is there a method to
avoid this?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options