Rob:
Thank you much! It was a real learning experience for me to build it that
way (you shoulda seen the one that got away, so to speak!) 8).
--
Murray
"Rob Giordano (aka: Crash Gordon®)" <
[email protected]>
wrote in message Murray...OT...but I like your web. Nice, clean layout.
| This is a tough problem facing people who are just designing pages with
| tables, as you have.
|
| I use CSS to build containers that can (more or less) accommodate text
size
| changes. You can see this in action at my site -
|
http://www.great-web-sights.com. Trying to do the same thing with tables
| alone can be tricky (there are no tables on that page, for example).
|
| On your page, you have text in absolutely positioned divisions -
|
|
| <td valign="top" width="100%">
| <!-- MSCellFormattingType="content" -->
| <div style="position: absolute; width: 200px;and this is going to be
| what is responsible for your problems. Here's why -
|
| Any absolutely positioned element is removed from the flow of the code on
| the page. This means that this content division will neither be affected
by
| changes to the surrounding table, nor will changes to it affect the
| surrounding table. But this is just what you want to happen - you want
the
| text size increase to cause the table to expand vertically. By placing
that
| content into a positioned div, you have prevented that from happening.
|
| What's worse is that you have put that division INSIDE the table. The
| number 1 rule of working with positioned elements is that you must not put
| absolutely positioned things directly inside tables. By doing that, you
| guarantee browser rendering inconsistencies between Macs and PCs.
|
| The same analysis would apply for your "layer1" div where the header is.
|
| Your layer2 is not affected by text size changes because it only contains
| your menu buttons. But, it too is inside the table.
|
| The solution to the immediate problem is to remove the layer code from the
| table and to drop it back onto the page (I usually put it immediately
above
| the </body> tag). Since these elements are absolutely positioned, their
| location in the flow of the code is immaterial.
|
| To solve the longer term problem, I would just put all of that content
| (minus the layers) back into the table, and see how that works.
|
| --
| Murray
|
| | > Then how do I avoid this situation? What do you
| > recommend?
| >
| >>-----Original Message-----
| >>Not a good decision. Search engines cannot read graphic
| > text. Furthermore,
| >>you will quickly ramp the weight of your page by doing
| > this.
| >>
| >>--
| >>Murray
| >>
| >>| >>>I found that out before you responded. Thanks.
| >>>
| >>> I'll have to use graphics for a more consistent feel.
| >>>
| >>> M
| >>>
| >>>
| >>>>-----Original Message-----
| >>>>Browser text size would be my guess....
| >>>>
| >>>>--
| >>>>Murray
| >>>>
| >>>>| >>>>>I checked, and I do in fact have Tahoma installed on
| > my
| >>>>> machine at home. I can try to use more reliable
| > fonts
| >>> to
| >>>>> work around the problem.
| >>>>>
| >>>>> What would cause the fonts to look different from one
| >>>>> machine to the next, assuming the fonts are installed
| >>> on
| >>>>> both machines?
| >>>>>
| >>>>> Thanks,
| >>>>> Marc
| >>>>>
| >>>>>>-----Original Message-----
| >>>>>>Is it possible you do NOT have Tahome installed on
| > your
| >>>>> machine at home? In
| >>>>>>this case, that character face would look *EXACTLY*
| >>> like
| >>>>> Times, since that
| >>>>>>is what your browser will use when it can't find the
| >>>>> font you have
| >>>>>>specified.
| >>>>>>
| >>>>>>Looking at your code, I can see that you have
| > specified
| >>>>> two fonts on the
| >>>>>>page - Garamond (this one is *not* web safe), and
| >>> Tahoma
| >>>>> (this one is
| >>>>>>*sorta* websafe). I would only use the Garamond face
| >>> if
| >>>>> I specified
| >>>>>>alternative fonts, e.g., <font face=garamond,
| >>>>>>verdana,arial,helvetica,sans-serif....
| >>>>>>
| >>>>>>> It looks consistent on
| >>>>>>> the button bar on the right.
| >>>>>>
| >>>>>>Of course - those are graphics.
| >>>>>>
| >>>>>>--
| >>>>>>Murray
| >>>>>>
| > message
| >>>>>>| >>>>>>> Here is the URL:
| >>>>>>>
http://home.comcast.net/~maxnax/connect-consulting/
| >>>>>>>
| >>>>>>> The look and feel of the font appear to be correct
| > on
| >>>>>>> this machine (particularly the text on the right
| >>>>> vertical
| >>>>>>> frame, but on my machine at home where I designed
| >>> this
| >>>>>>> site, it resembled Times instead. It looks
| >>> consistent
| >>>>> on
| >>>>>>> the button bar on the right.
| >>>>>>>
| >>>>>>> Thanks in advance.
| >>>>>>> M
| >>>>>>>
| >>>>>>>>-----Original Message-----
| >>>>>>>>I have never seen Tahoma not display properly. Can
| >>> you
| >>>>>>> show me a page where
| >>>>>>>>this happens?
| >>>>>>>>
| >>>>>>>>--
| >>>>>>>>Murray
| >>>>>>>>
| >>>>>>>>"Marc A." <
[email protected]>
| > wrote
| >>>>> in
| >>>>>>> message
| >>>>>>>>| >>>>>>>>> I'm not sure if this is FrontPage specifically,
| > or
| >>>>>>>>> Windows XP in general, but some fonts such as
| >>> Tahoma
| >>>>> do
| >>>>>>>>> not display correctly. As a result the text of
| > my
| >>>>>>>>> website looks skewed on other PCs. Any ideas?
| >>>>>>>>
| >>>>>>>>
| >>>>>>>>.
| >>>>>>>>
| >>>>>>
| >>>>>>
| >>>>>>.
| >>>>>>
| >>>>
| >>>>
| >>>>.
| >>>>
| >>
| >>
| >>.
| >>
|
|
