![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Line height *is* a bit tricky and it is best not to use it (except at the body level - sans units - to slightly increase it for the reasons JK gives) unless you understand a few basics about it in a bigger context than: "putting *this* line-height *here* makes the distance between this and that text on *my* browser seem about right...". The reason it is OK to keep out of what can be a hornet's nest is that *perfectly serviceable* line heights are naturally used by the browser. These days, browsers use a hidden but very detailed default stylesheet (like yours in the head of your doc, but much more comprehensive). These stylesheets are the product of a lot of intelligence and it is only safe to change the defaults if you are confident you can do better. |
#12
| |||
| |||
|
|
Adrienne Boswell wrote: A few things: 1. dorayme <snip 2. This <snip 2. Usenet <snip 3? ;-) |
#13
| |||
| |||
|
|
A few things: 1. dorayme <snip 2. This <snip 2. Usenet <snip 3? ;-) Yep. Three is the number of things thou shalt list. |
#14
| |||
| |||
|
|
Line-height doesn't usually even appear in the default stylesheet. The initial value (which is "normal") is fairly normal, and good enough for most normal purposes. |
#15
| |||
| |||
|
|
[Whoosh!] |
|
I guess "Monty Python and the Holy Grail" was not terribly popular in Finland? |
#16
| |||
| |||
|
|
Ben C wrote: Line-height doesn't usually even appear in the default stylesheet. The initial value (which is "normal") is fairly normal, and good enough for most normal purposes. No, the value normal tends to be too small for the commonly used fonts and line lengths. |
#17
| |||
| |||
|
|
On 2009-10-29, dorayme <doraymeRidThis (AT) optusnet (DOT) com.au> wrote: [...] Line height *is* a bit tricky and it is best not to use it (except at the body level - sans units - to slightly increase it for the reasons JK gives) unless you understand a few basics about it in a bigger context than: "putting *this* line-height *here* makes the distance between this and that text on *my* browser seem about right...". The reason it is OK to keep out of what can be a hornet's nest is that *perfectly serviceable* line heights are naturally used by the browser. These days, browsers use a hidden but very detailed default stylesheet (like yours in the head of your doc, but much more comprehensive). These stylesheets are the product of a lot of intelligence and it is only safe to change the defaults if you are confident you can do better. Line-height doesn't usually even appear in the default stylesheet. The initial value (which is "normal") is fairly normal, and good enough for most normal purposes. |
#18
| |||
| |||
|
|
In article <slrnheik1s.334.spamspam (AT) bowser (DOT) marioworld>, Ben C <spamspam (AT) spam (DOT) eggs> wrote: On 2009-10-29, dorayme <doraymeRidThis (AT) optusnet (DOT) com.au> wrote: [...] Line height *is* a bit tricky and it is best not to use it (except at the body level - sans units - to slightly increase it for the reasons JK gives) unless you understand a few basics about it in a bigger context than: "putting *this* line-height *here* makes the distance between this and that text on *my* browser seem about right...". The reason it is OK to keep out of what can be a hornet's nest is that *perfectly serviceable* line heights are naturally used by the browser. These days, browsers use a hidden but very detailed default stylesheet (like yours in the head of your doc, but much more comprehensive). These stylesheets are the product of a lot of intelligence and it is only safe to change the defaults if you are confident you can do better. Line-height doesn't usually even appear in the default stylesheet. The initial value (which is "normal") is fairly normal, and good enough for most normal purposes. Good point. As with many other presentational matters, there are initial values set by the browser via internal coding, sometimes in conjunction with user preferences or options. |
#19
| ||||
| ||||
|
|
The initial values are all in the CSS specification, and the browser _has_ to do those as printed |
|
Then for anything that differs from those values, there's the default stylesheet, which is up to the individual browser, but usually mostly the same, |
|
and the spec suggests a default stylesheet. |
|
Observe that the default stylesheet does not set span to display: inline-- it doesn't need to, because the initial value of display is inline. |
#20
| |||
| |||
|
|
On 2009-10-29, dorayme <doraymeRidThis (AT) optusnet (DOT) com.au> wrote: In article <slrnheik1s.334.spamspam (AT) bowser (DOT) marioworld>, Ben C <spamspam (AT) spam (DOT) eggs> wrote: On 2009-10-29, dorayme <doraymeRidThis (AT) optusnet (DOT) com.au> wrote: [...] .... As with many other presentational matters, there are initial values set by the browser via internal coding, sometimes in conjunction with user preferences or options. The initial values are all in the CSS specification, and the browser _has_ to do those as printed (see the "full property table" in one of the appendices). |
![]() |
| Thread Tools | |
| Display Modes | |
| |