This is not a doctype problem. It is a basic method problem.
Your method is just not the right one. Why? Because any
resizing of text
will cause the content in the absolutely positioned elements
to OVERFLOW the
contents below them. That is why, with the 5-minute page I
posted, when you
resize the text, the content below is pushed down. There is
no absolute
positioning there. HOWEVER, the page I posted is not the
finished version
either - resizing the text causes horizontal overflow, and
that's because I
had to give each menu element an assigned width. When the
contents are
larger than can be accommodated by that width, they overflow.
The right way
to manage that is a bit more complex, and would involve using
both text and
images for that menu.
To fix the horizontal overflow problem, you would set the
menu up as an
unordered list. You would float:left the list elements as I
have done, and
remove the bullets using CSS. Then you would give each list
element its own
background image that is a graphic of the text for that link.
Now you have
an anchor in the list element that contains the same text for
that link, but
you indent that <a> tag's contents -1000px left. Thus,
the text is not
seen, and the background image is. Now you can resize your
text till the
cows come home and the menu will be unaffected.
> the way you have those setup in your solution, they wrap
around
> according to the vertical width of the browser.
That's easy to fix by putting each of those elements within a
fixed width
container. Now the contents are unaffected by the horizontal
browser
viewport dimensions.
Make sense?
--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"MLBdesigner" <webforumsuser@macromedia.com> wrote in
message
news:fe0dub$gv9$1@forums.macromedia.com...
> Hi Murray,
>
> First of all - I thank you for responding! However, this
issue continues
> to
> stump me. I took a look at what you put together, and it
has several
> issues
> that (if at all possible) I would appreciate you or
someone else
> commenting on.
> [Or for someone to suggest yet a different solution
altogether.]
>
> 1) The placement problem under FireFox [item 1) in my
original message]
> still
> occurs using your solution on some hi-res monitors (like
my laptop) - just
> not
> as badly. For example, the links from your version for
"Discussion
> Forums" and
> "Reader Feedback" bleed together, and "Women's View" has
a gap in the
> center
> row.
>
> 2) Using your approach, the betahometop actually looks
DIFFERENT in the
> different browsers, depending on which browser and
display I am using.
> For
> example, on my desktop - they all do look the same ...
which is identical
> to my
> own current solution. On my laptop (with the hi-res
display FireFox
> issue I
> originally described), FireFox still somewhat has the
overlapping text
> issue
> [1) immediately above], plus IE7 has a one-line gap
between "Your Midlife"
> and
> "Crisis" ... while Safari and FireFox do not.
>
> In other words, using your solution - I seem to have
less uniformity in
> terms
> of appearance across the different browsers and
displays.
>
> The other thing to mention is that I DO want absolute
positioning for all
> the
> menu items across the top, and also for the google
search bar, and the
> 468x60
> ad ... the way you have those setup in your solution,
they wrap around
> according to the vertical width of the browser.
>
> After I posted my original message, I continued to dig
around, and found
> this
> thread on webdeveloper.com:
>
>
http://www.webdeveloper.com/forum/showthread.php?t=116620
>
> and studied the link that was suggested to that user for
adjusting his
> DTD:
>
>
http://www.w3.org/QA/2002/04/valid-dtd-list.html
>
> I tried various combinations (hoping it was just a DTD
issue), but nothing
> cured the problem. Not sure if anyone would like to
comment on whether
> the
> DTD would solve my problem, or not - as I came up empty.
>
> You do have me thinking about the effect of text size on
everything -
> which
> had not occurred to me previously. I suppose I either
need to plan for
> increasing/descreasing text size, or specifically decide
not to support
> it.
>
> I'm pretty much a novice at all of this - so please feel
free to point out
> any
> ignorance I may be exhibiting. Thanks to anyone who can
help me ... ;o)
>
> Greg
>