Hi, I appreciate all the advice I am getting on this topic and it's raising some very important issues for me and I think the template creators too. I understand setting the line-height as a ratio, and the font sizes could still be set as pixels (or should this be a ratio too?). I am however concerned that because of the width of the menu, it being a drop-down, the number of items, and the layout having a fixed width that another serious issue is that items start breaking out of their containers (applys to the height too of course). I would to think that having a flexible/fluid/expandable menu - possibly sitting outside of the main wrapper (with a minimum width declared in pixels) could resolve this issue. Other items that have a set width (e.g. my top panel trigger) could be set to min-widths.
Could css-d give me some examples of what you think are the best kind of declarations for items such as menu links (horizontal, 1 line) using ratios and whatever else so that I do not run into problems with min font sizes. It'll just give me a starting point and then I can play about with it in fire-bug. Just as I thought it was the end of IE6 I run into a new problem! Lovin' web design :D Thanks, CB On 13/07/2010, at 2:53 PM, Felix Miata wrote: > On 2010/07/13 13:52 (GMT+0800) Chris Blake composed: > >> 2. 'line-height set in pixels' - what should I use? It's a menu >> rather >> than a paragraph. > > Unless you're happy to have your design break royally upon > encountering > minimum font size, containers need to be big enough for the text they > contain. Line-height is a sort of containment. When you specify line- > height > of 16px and my minimum font size is 22px, something will definitely > break. > That break is likely to be my patience, followed by a click on the > back button. > > So, make the line-height depend on the size of the text it must > contain, > using a ratio, a plain number, such as 1.3. > http://www.w3.org/TR/CSS21/visudet.html#propdef-line-height > >> 16 pixels minimum - are you kidding me!? > > Pixels are a proportion of a display canvas that is normally of > unknown size. > Since CSS cannot know display size regardless, and cannot know total > px to > fit in the unknown display space, via CSS alone you have no idea how > big 16px > is. At 144 DPI (e.g, my display here), 16px is only 8pt, while my UI > text > (e.g. browser menus) is 10pt, and my normal browser minimum font > sizes vary > between 15px and 22px, depending on which browser and for what > purpose I'm > using it. Sometimes I set the minimum equal to the (24px) default, > which > removes any practical possibility of contextual meaning to be > derived from > text size, but is the only way to actually read what I need to read > without > disabling all page styles. > > On http://blakeys.com/design/index.php/en/blakeys-websites-introduction > with > a 22px minimum setting the white nav text is so scattered about it's > impossible to guess what it means to offer, and on hover the dropdowns > compound the apparent textual randomization. Up top in the middle > looks like > a tiny hanging tab, with only about the top 40% of the text it's > apparently > supposed to contain actually showing, and nothing showing to help > explain it > on the statusbar on hover. The search box can't fit even 7 full > letters > (abcdefg), cutting off the bottoms, and one or the other end. > -- > "The wise are known for their understanding, and pleasant > words are persuasive." Proverbs 16:21 (New Living Translation) > > Team OS/2 ** Reg. Linux User #211409 > > Felix Miata *** http://fm.no-ip.com/ ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
