![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Christoph Paeper said: My feeling is you set your preferred font size too low, theres nothing wrong with my font size. whats wrong is authors telling me should really be 10% smaller. |
|
i don't like authors telling me what my font size should be (or how long the lines of text should be). stop trying to control me. |
|
you have a killfile, |
#12
| |||
| |||
|
|
C A Upsdell wrote: "kchayka" <usenet (AT) c-net (DOT) us> wrote in message news:2vstebF2oggguU1 (AT) uni-berlin (DOT) de... % units do not trigger the "insanely small" text size problem in WinIE. Only em units do. Wrong. Once upon a time, I did use % units, and I did have endless shrinking text size problems Caused by using a body text size smaller than 100%? Doctor, it hurts when I do this... |
#13
| |||
| |||
|
|
In comp.infosystems.www.authoring.stylesheets C A Upsdell said: and switching to small, x-small, etc. stopped this problem for good. the problem with keywords is that browsers don't use the same base size. just as kchayka said. |
|
The inconsistency is in IE, easily overcome. And the CSS trickery which overcomes this inconsistency can be copied and pasted from site to site, changing only the selectors, as needed. or you could just use % and not fart around with unneeded hacks. |
#14
| |||
| |||
|
|
C A Upsdell wrote: Wrong. Once upon a time, I did use % units, and I did have endless shrinking text size problems (at least with some browsers) Which? I'd like to know, as I've never encountered such issues. |
#15
| |||
| |||
|
|
C A Upsdell wrote: "Beauregard T. Shagnasty" wrote 90%, that is. Not if it is nested, which what the OP was concerned with. 90% of 90% of 90% ... can quickly become too small to read ... So, apply font-size more logically. Do you need to apply a 90% in a 90% in a 90%, ever? Normally, I set font-size for the body (at 100%) and set special things at say 90%. If you never nest this upon itself, you avoid the problem. think you're inventing an unrealistic problem. |
#16
| |||
| |||
|
|
C A Upsdell wrote: "kchayka" <usenet (AT) c-net (DOT) us> wrote in message news:2vt2frF2nis53U1 (AT) uni-berlin (DOT) de... You put a bandaid on it by using font-size keywords instead of %. But you're only treating the symptoms, not the problem. The symptoms are a progressively smaller font-size with nested elements. The problem is setting explicit sizes less than 100%. Stop doing that and the symptoms disappear. |
#17
| |||
| |||
|
|
"Neal" wrote C A Upsdell wrote: I did use % units, and I did have endless shrinking text size problems Which? A very worthy question. Unfortunately I can't show you... I hope that you will believe me when I say that I have re-confirmed that such % problems exists in the sites, and that the problems occurred ONLY with certain browsers whose compliance with standards is (ahem!) not admirable. |
#18
| |||
| |||
|
|
"Neal" <neal413 (AT) yahoo (DOT) com> wrote in message news pshi9tiz46v6656 (AT) news (DOT) individual.net...C A Upsdell wrote: "Beauregard T. Shagnasty" wrote 90%, that is. Not if it is nested, which what the OP was concerned with. 90% of 90% of 90% ... can quickly become too small to read ... So, apply font-size more logically. Do you need to apply a 90% in a 90% in a 90%, ever? Normally, I set font-size for the body (at 100%) and set special things at say 90%. If you never nest this upon itself, you avoid the problem. think you're inventing an unrealistic problem. Not inventing. Note my response to another of your messages in which I confirmed the problem ... with some browsers. |
#19
| |||
| |||
|
|
1) and 2), and 3) and 4), should be the same size, one calculated in the browser, the other calculated by hand and set as a direct size. |
#20
| |||
| |||
|
|
C A Upsdell wrote: Wrong. Once upon a time, I did use % units, and I did have endless shrinking text size problems (at least with some browsers) Which? I'd like to know, as I've never encountered such issues. |
![]() |
| Thread Tools | |
| Display Modes | |
| |