Font Resizing In Browser

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Another "newbie" here. :o)
Just discovered that if someone changes their font size option in IE, then
some of my page formatting get's a little wack.
Is there a means to default your page (via Frontpage design) to be viewed at
Medium (or a given general option)?

Thank you in advance, for your help.
 
Hmmm

I am certainly not an expert by any means. I am replying because it is an
inteersting question and others may throw in some thoughts.

I am wondering how you format your page. The thought occurs to me that if
you use percentages, then any resizing *should* adjust. I would have thouht
that using pixels would also do the same.

Any experts out there ?
 
You cannot stop users resizing their browsers, or changing the fonts
and font sizes. The answer is to test your pages using different
browser window widths, and changing the font-size yourself to see the
effect, then adjust the page to allow for this.

Avoid Absolute Positioning, unless you fully understand how it works.
Likewise, avoid WordArt, textboxes and any other shapes or objects
created from the FrontPage drawing toolbar. All these use absolute
positioning (and VML graphics which only display in IE5.5 and later -
other browsers will display nothing or very low quality .gif
representations).

If users resize the font, it usually so they can read the text
easily - is your text too small?
 
Thank you Trevor, Ronx, and E.T. for your responses.
I seem to run into more problems with that "absolute positioning" option
then seems to be good. What are the advantages of this feature anyway?

I know that each of the areas (text box and grouped drawing images) I am
having concerns with are set to this option, so I will be sure and remove it
this evening when I get home. :c)

Also appreciate your guidance to additional education! Fingers - crossed,
all will be well soon?

Thanks again!!
 
This may help you understand positioning a bit -

There are 4 different types of positioning:
Absolute
Relative
Fixed
Static

Here is a brief explanation of each kind of positioning (with regard to
placement of elements on the page only)....

Position:absolute (or A/P elements)
-----------------------
This does several things -
1. It 'removes' the element from the flow of the code on the­ page so that
it can no longer influence the size or position of any other pa­ge element
(except for those contained within it, of course).

2. The absolutely positioned element takes its position from the position of
its closest PA­RENT *positioned* element - in the absence of any explicitly
positioned parent, this will default to the <body> tag, which is always
positioned
­at 0,0 in the browser viewport.

This means that it doesn't matter where in the HTML code the laye­r's code
appears (between <body> and </body>), its location on the screen will not
change (this assumes that you have not positioned the A/P element within
a table or another A/P element, of course). Furthe­rmore, the space in
which
this element would have appeared were it not positi­oned is not preserved
on the screen. In other words, absolutely positioned elements don't take
up any space on the page. In fact, they FLOAT over the page.

Position:relative (or R/P elements)
----------------------
In contrast to absolute positioning, a relatively positioned page element is
*not* removed from t­he flow of the code on the page, so it will use the
spot
where it would have­ appeared based on its position in the code as its
zero point reference. If­ you then supply top, right, bottom, or left
positions
to the style for this ­element, those values will be used as offsets from
its
zero point.

This means that it DOES matter where in the code the relativ­ely positioned
element appears (, as it will be positioned in that location (­factoring in
the offsets) on the screen (this is true for any placement in the code).
Furthermore, the space where this e­lement would have appeared is
preserved in the display, and can therefore­ affect the placement of
succeeding elements. This means that the taller a relatively
positioned element is, the more space it forces on the page.

Position:static
-------------------
As with relative position, static positions also "go with ­the flow". An
element with a static position cannot have values for offset­s (top, right,
left, bottom) or if it has them, they will be ignored. Unless explicitly
positioned, all div elements default to static positioning.

Position:fixed
------------------
A page element with this style will not scroll as the page c­ontent scrolls.
Support for this in elements other than page backgrounds is ­quirky

There are several other things you need to know:

1. ANY page element can be positioned - paragraphs, tables, images, lists,
etc.
2. The <div> tag is a BLOCK level tag. This means that if it is not
positioned or explicitly styled otherwise, a) it will always begin on a new
line on the screen, and b) it will always force content to a new line below
it, and c) it will always take up the entire width of its container (i.e.,
width:100%).
3. The placement of A/P elements *can* affect the BEHAVIOR of other
elements
on the page. For example, a 'layer' placed over a hyperlink will mask that
hyperlink.

You can see a good example of the essential difference between absolute and
relative positioning here -

http://www.great-web-sights.com/g_layersdemo.asp

There is a good place for each kind of positioning, and a good reason for
using each.....
 
Back
Top