Re: [css-d] font-sizing bug in generated content in IE 10 ?
I've been thinking about this issue since it was first posted because it seems to relate, at least a bit, to a bug in IE9 and 10 that I reported late last year. See IE bug ID 772679 http://connect.microsoft.com/IE/feedback/details/772679/ie10-not-recognizing-font-decloration-when-rem-is-used-as-font-size-unit-of-measure . In thebug IE won't use the REM unit in any font-size rule including the font shorthand syntax. In fact does it not use the REM it completely ignores the entire font related rule and falls all the way back to its default serif or sans-serif skipping the full stack. Interestingly, IE will use the REM unit to size elements (as I do regularly). I battled with their bug reporting system for months, it kept closing the bug with 'as designed' and I had to keep reactivating it. Finally I contacted out Fearless and Famous Leader, Mr. CSS Wizard himself, Eric Meyer who talked to some IE Engineers he knows who then started working on the issue via internal bug IDsMany thanks Eric!! Anyway, this issue shines another light on the whole problem in IE. As I recall generated content is handled differently by the UA's parser. My guess is that when generated content is present a header is added to it before it enters the CSS parser and this header contains information that then allows IE to recognize and use the REM unit. I'll add a note to the bug ID containing the info from this problem...maybe it will help them id and fix the bug faster. In the meantime the only work-around that I've found is to include a font-sizing rule using pixels before one using REMs. Yes, I know it's a pain but the REM unit is just too powerful and flexible to let EM get in the way. Hope that helps a bit, Eric __ css-discuss [css-d@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/
Re: [css-d] font-sizing bug in generated content in IE 10 ?
Le 26 avr. 2013 à 00:17, Gabriele Romanato gabriele.roman...@gmail.com a écrit : You first declared a font-size on a type selector, p, with a pseudo-element, then you declared a class with another pseudo-element on the same element type The font-size is applied on the pseudo-element, not on the p. For both paragraphs the pseudo-element should compute the font-size based on the parent element. Yukka wrote: This looks definitely like a bug to me. The main practical issue with it is that we don’t know what really triggers it, so we can’t say for sure how to avoid or circumvent it. Definitely a bug. And IE 9 has the same issue. Surprisingly, IE 8 has it right (when substituting the CSS2.1 notation using a single column). And no, using the CSS2.1 notation does not make it work in IE 9 and 10… No idea what secret sauce the MSIE team has added in the mix, so I can't suggest any possible workaround. Philippe -- Philippe Wittenbergh http://l-c-n.com __ css-discuss [css-d@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/
Re: [css-d] font-sizing bug in generated content in IE 10 ?
On 26.04.2013 05:00, Philippe Wittenbergh wrote: No idea what secret sauce the MSIE team has added in the mix, so I can't suggest any possible workaround. This IE bug makes me break the convention not to use fixed font-size on web pages, applying font-size in px on the generated content in IE9+ only - hacked in. Seems to work reasonably well. regards Georg __ css-discuss [css-d@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/
Re: [css-d] font-sizing bug in generated content in IE 10 ?
Georg wrote: This IE bug makes me break the convention not to use fixed font-size on web pages, applying font-size in px on the generated content in IE9+ only - hacked in. Seems to work reasonably well. Better than rem, Georg ? Having been forced to use rem for this fix, I am now considering adopting them more widely. Philip Taylor __ css-discuss [css-d@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/
Re: [css-d] font-sizing bug in generated content in IE 10 ?
On Fri, Apr 26, 2013 at 2:35 PM, Philip TAYLOR p.tay...@rhul.ac.uk wrote: Georg wrote: This IE bug makes me break the convention not to use fixed font-size on web pages, applying font-size in px on the generated content in IE9+ only - hacked in. Seems to work reasonably well. Better than rem, Georg ? Having been forced to use rem for this fix, I am now considering adopting them more widely. Philip Taylor Support isn't too bad for rem. What's best practice fall back for using rem? -- Tom Livingston | Senior Front-End Developer | Media Logic | ph: 518.456.3015x231 | fx: 518.456.4279 | mlinc.com __ css-discuss [css-d@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/
Re: [css-d] font-sizing bug in generated content in IE 10 ?
On 26.04.2013 14:35, Philip TAYLOR wrote: Better than rem, Georg ? Having been forced to use rem for this fix, I am now considering adopting them more widely. Haven't bothered to test out what's best in bug-cases like this, only what works and seem to do no real harm. The rem unit do look better on paper though. regards Georg __ css-discuss [css-d@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/
Re: [css-d] font-sizing bug in generated content in IE 10 ?
You wrote: font-size: 0.5rem. Is it a typo? Anyway, I think it's somewhat related to the cascade and inheritance behavior when applied to pseudo-elements. You first declared a font-size on a type selector, p, with a pseudo-element, then you declared a class with another pseudo-element on the same element type (p). The point is that they're both Ps, so they inherit from each other. This is a controverted question. I think this IE's behavior **might** be correct. On Thu, Apr 25, 2013 at 12:41 PM, Philip TAYLOR p.tay...@rhul.ac.uk wrote: Please take a look at : http://hellenic-institute.rhul.ac.uk/research/Etheridge-development/Test/ (transcript below) and compare its appearance in IE 10 and another browser (I use Seamonkey; it will almost certainly appear in Firefox as it does in Seamonkey, as they use the same rendering engine). If you use page zoom (Ctrl +) to make everything clearly visible, you will see that in IE, the generated content on line two is about one half of the generated content on line one, whilst the generated content on line four is exactly the same size as that on line three. Lines one and two use em units for the generated content, lines three and four use rem units. The only difference between the first and second line of each pair is that the P element is placed in a class, and the CSS rule applies both to the classless and classed P elements. It seems to me that IE may be incorrectly applying the font-size attribute of the rule twice in the case of the classed P elements (but not the content attribute) -- once for the P and once for the class; what do others think ? Philip Taylor !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01//EN http://www.w3.org/TR/html4/strict.dtd; HTML HEAD META http-equiv=Content-Type content=text/html; charset=utf-8 TITLEIE generated content test/TITLE STYLE type=text/css DIV.em P::before, DIV.em P.EOF::before {font-size: 0.5em; content:em-units: } DIV.rem P::before, DIV.rem P.EOF::before {font-size: 0.5rem; content:rem-units: } /STYLE /HEAD BODY DIV class=em PLine one/P P class=EOFLine two/P /DIV DIV class=rem PLine three/P P class=EOFLine four/P /DIV /BODY /HTML __ css-discuss [css-d@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/ -- Gabriele Romanato Referente IWA ITALY - Regione Abruzzo International Webmasters Association Italia http://www.iwa.it | e-mail: abru...@iwa.it Professionista Web - Legge 4/2013 http://gabrieleromanato.com/ http://gabrieleromanato.name/ (English) __ css-discuss [css-d@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/
Re: [css-d] font-sizing bug in generated content in IE 10 ?
2013-04-25 18:17, Gabriele Romanato wrote: You wrote: font-size: 0.5rem. Is it a typo? I’m pretty sure Philip intentionally tested both with em and with rem. The bug manifests itself when em is used, not when rem is used, suggesting that IE 10 indeed calculates em wrong, when there is a pseudo-element with a class and font-size is set on it using the em unit. Anyway, I think it's somewhat related to the cascade and inheritance behavior when applied to pseudo-elements. There is no inheritance involved when a property is set on an element. You first declared a font-size on a type selector, p, with a pseudo-element, then you declared a class with another pseudo-element on the same element type (p). The point is that they're both Ps, so they inherit from each other. No, they don’t. Elements only inherit from their parents. And selectors are not elements. I think this IE's behavior **might** be correct. This looks definitely like a bug to me. The main practical issue with it is that we don’t know what really triggers it, so we can’t say for sure how to avoid or circumvent it. Yucca __ css-discuss [css-d@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/
Re: [css-d] font sizing and ie 7 alignment help please!
Melinda Odom wrote: Hi, I am having a terrible time with font sizing in all browsers because I want a fixed width and height site. Page is: http://www.designhosting.biz/support2.html The left column is only text. The right is a css scrolling menu. Using percentages on the body tag shows good in mozilla and safari but looks terrible in opera. At the ie rendering site the text is longer using ie 8. Also ie 7 shows the navigation buttons at the top higher off the ledge. I tried points for the text style which seems to show the best but don't know if this is good. I tried pixels and ems but get about the same results or worse. Is there a way to keep the fonts all the same? I see on other sites they look about the same in safari, mozilla, and opera browsers. Thanks! Best Regards, Melinda Odom Delete the height on the outermost wrapper (let the content determine height): #container { border: 1px solid red; -- :: 4 position only-- delete padding-bottom: 40px; : : add rule width: 980px; margin-right: auto; margin-left: auto; height: 460px; :: delete background-color: #FFFCF7; } Re-set the font-size, and the font-stack, on the body declartion to: body { background-color: #F7F4EE; background-image: url(bg_body0.jpg); background-repeat: repeat; color: #514E4C; font-family: Arial, Helvetica, sans-serif; -- :: delete font-size: 80%; -- :: delete line-height: 1.5; -- :: delete font: normal 100%/1.4 Helvetica Neue, Helvetica, Arial, sans-serif; - :: add rule } In other words feed Macs Helvetica Neue, Helvetica; and, feed PCs Arial. Feed all OS default 100% on 1.4 line-height. Use percent thereafter throughout the style sheet on individual selectors. If you are pimping accessibility then normally primary content p is 100%, secondary content p is 95%, and tertiary content p is 90%. Once you get worked out, bring it back. Someone will help with remaining corrections for IE/7. Best, ~d __ 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/
Re: [css-d] Font sizing
At 10:51 PM 2/17/2009 -0500, Felix Miata wrote: ...have nothing to do with the Golden Section, and to me would look I have to wonder if more than a tiny fraction of professional web designers know that that is. Probably far fewer of the zillion hack designers or the junkware they use to create would. Well, for those here who don't know what the Golden Section is, if it's any consolation I haven't got a clue what people are talking about here on this list half the time either! ;) With the assumption that you know what I'm referring to, though, you subsequent points do bring up a whole other can of worms for me... All rendering engines round nominal font sizes to whole numbers of px, but not all browsers use equivalent rounding methods. IE, the dominant overall representative, truncates every computed px size to a whole number, while some popular other browsers use something resembling the mathematical rounding most of us learned when we graduated from simple fractions to decimals in school. This is actually very frustrating to me (now). For all these many past years, I've had my base font size set at 14px -- this was, for the longest time, the recommended size (in px) for general readability. Since being on this list, I've learned that this recommendation is no longer valid, and percentages (specifically 100% for one's base font) are the recommended way to go instead of px. However, when I was doing my font sizing using px, I could very easily size my text, headings, etc. with specific whole, rounded numbers (9px, 14px, 23px, 37px, etc.) no problem at all, but from what you've pointed out, if I start doing things using the far more vague percentages values, then things will simply not quite look as I might expect/hope from one platform/browser to another. So this is all rather ironic: in order to get things to look right, I have to do them in the wrong way (using px), but in order to do them in the right way (using %), then I'll never be sure that it actually looks right (in fact, I'm virtually guaranteed that things will look wrong for some people). Argh...! Ron :/ Woof?... http://www.Psymon.com Ach, du Leni!... http://www.Riefenstahl.org Hmm... http://www.Imaginary-Friend.ca __ 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/
Re: [css-d] Font sizing
Ron Koster wrote: So this is all rather ironic: in order to get things to look right, I have to do them in the wrong way (using px), but in order to do them in the right way (using %), then I'll never be sure that it actually looks right (in fact, I'm virtually guaranteed that things will look wrong for some people). Ron :/ What's so difficult about keeping it simple and honoring user default? body {font: 100%/1.4 sans-serif;} #primary-content p {/*inherits default*/ } #secondary-content p {font-size:95%;} #tertiary-content p {font-size:90%;} h1,h2,h3,h4,h5,h6 {/*set in whatever percent value rocks your boat*/} -- A thin red line and a salmon-color ampersand forthcoming. http://chelseacreekstudio.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/
Re: [css-d] Font sizing
Where did you get 14px as the recommended size for general readability? I've been creating websites since 1993 and never recall seeing that size mentioned. Browser defaults usually equal the operating system default which is on Windows 16px and on Macs prior to OS X generally 12px (Macs with their desktop publishing focus used 1px = 1pt so you could actually hold a ruler to the screen to measure but I digress). Having been concerned with accessibility I've been using ems or percentages since 2001 but then I've never been that concerned if there is a slight difference between one browser and another and I don't expect the web to be like print. As far as I'm concerned it the end result is attractive does a pixel or two difference between two browser really matter? After all people will only see the site in their browser of choice unless it is broken in that browser or they are a web professional who has a reason to check in multiple browsers. Cheryl D Wise -Original Message- From: Ron Koster This is actually very frustrating to me (now). For all these many past years, I've had my base font size set at 14px -- this was, for the longest time, the recommended size (in px) for general readability. Since being on this list, I've learned that this recommendation is no longer valid, and percentages (specifically 100% for one's base font) are the recommended way to go instead of px. However, when I was doing my font sizing using px, I could very easily size my text, headings, etc. with specific whole, rounded numbers (9px, 14px, 23px, 37px, etc.) no problem at all, but from what you've pointed out, if I start doing things using the far more vague percentages values, then things will simply not quite look as I might expect/hope from one platform/browser to another. So this is all rather ironic: in order to get things to look right, I have to do them in the wrong way (using px), but in order to do them in the right way (using %), then I'll never be sure that it actually looks right (in fact, I'm virtually guaranteed that things will look wrong for some people). Argh...! Ron :/ Woof?... http://www.Psymon.com Ach, du Leni!... http://www.Riefenstahl.org Hmm... http://www.Imaginary-Friend.ca __ 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/ __ 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/
Re: [css-d] Font sizing
Ron Koster wrote: So this is all rather ironic: in order to get things to look right, I have to do them in the wrong way (using px), but in order to do them in the right way (using %), then I'll never be sure that it actually looks right (in fact, I'm virtually guaranteed that things will look wrong for some people). Argh...! :-) If by wrong you mean: not exactly as you intended, then you're right. It may even end up as the end-user wants, or need, and there's nothing you or anyone else who design for the web can do about it. We web designers create illusions, but there's no reason for us to live in them. Pixel sized text doesn't guarantee the right size anywhere but on our own screen(s) and in our own browser(s), and that's just something all web designers _have to live with_ whether they like it or not. One day, when the average screen resolution is well above 300dpi, we may be able to fine-size text as we like - but only as a suggestion on a browser's default level. No end-users will have to honor our suggestions or use a browser and screen resolution etc. we are familiar with, so it'll still turn out wrong for us but right for them in many cases ... just as it should. It would be far worse if it turned out right for the designer but totally wrong for end-users for all time. There's enough designs that fit such a description out here already, and it would be good if we could break the cycle and let progress in technology work to our advantage - at all ends. regards Georg -- http://www.gunlaug.no __ 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/
Re: [css-d] Font sizing
At 08:03 AM 2/18/2009 -0600, Cheryl D Wise wrote: Where did you get 14px as the recommended size for general readability? I've been creating websites since 1993 and never recall seeing that size mentioned. That's basically when I started, too, and then I was on webdesign-l for many years (indeed, I was on it *before* it even started!), and that's essentially where I got it from. I really wish I had some URLs for you, but I can't seem to find any references in searching my own email archives. I do recall quite distinctly, however, that that figure (14px) was arrived at through various research done by some universities and stuff -- and, at *that* time (when CSS first arrived on the scene), there was also some legitimate reasoning for choosing px over em or %, too. Indeed, this was a BIG thing back at that time, with virtually everyone in the know insisting to go with 14px, and indeed there were various studies that could be pointed to for reference (I just don't know what/where they are any more -- sorry). And so, I took that well-researched, well-heeded advice, and for the next 10 years I did everything in a way that would ultimately prove to be wrong (in the long run -- although who knows where we'll be in another 10 years???). Ron :/ __ 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/
Re: [css-d] Font sizing
At 09:30 AM 2/18/2009 -0500, David Laakso wrote: What's so difficult about keeping it simple and honoring user default? body {font: 100%/1.4 sans-serif;} #primary-content p {/*inherits default*/ } #secondary-content p {font-size:95%;} #tertiary-content p {font-size:90%;} h1,h2,h3,h4,h5,h6 {/*set in whatever percent value rocks your boat*/} Sure! Why not?! But then what's the point in studying typography, and art, and aesthetics, and what's the point of trying to do anything with CSS and trying to get things to look good? The point that I was making -- what my question (and frustration) is -- is that as Felix pointed out, things can go screwy if/when one is using more vague specifications like 90% of some user's system default of 12pt (or whatever) in comparison to another platform and/or browser. If I specify all my various font sizes in pixels then everything will *proportionally* all be exactly how I want them to look, but if I use percentages then that's simply not the case -- that page that Felix created... http://fm.no-ip.com/auth/Font/font-rounding.html ...shows that issue perfectly. And hey, maybe these slight differences don't matter to you or others, but they matter to me. Perhaps I'm just being too picky, though, I don't know -- maybe I've hung around with type (font) designers too long, where it matters if that teeny-tiny serif that one can only see under a microscope is a billionth of a millimeter off. And as a graphic designer/digital artist, too, when I create a piece of artwork it can matter a great deal to me if a single pixel (out of thousands or millions) looks wrong. In that same regard, when I create a web site (for myself, at least) my desire is not just to create a repository to dump text/information, but to create a work of art, where viewing the text on the page (even if it was pure gibberish, or written in Arabic or Russian characters or something) is also visually pleasing to the eye. If I wanted to specify, say, my list items to be 85.4% of my base font size, then if they end up being 80% instead (because of the issues that Felix points out), well, to me it just wouldn't look right. Hence my frustration... Ron :/ __ 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/
Re: [css-d] Font sizing
On 2009/02/18 08:50 (GMT-0500) Ron Koster composed: However, when I was doing my font sizing using px, I could very easily size my text, headings, etc. with specific whole, rounded numbers (9px, 14px, 23px, 37px, etc.) no problem at all, but from what you've pointed out, if I start doing things using the far more vague percentages values, then things will simply not quite look as I might expect/hope from one platform/browser to another. Is this your ultimate goal: getting everything set up to fit into some particular combination of relationships that look nicely together, and hopefully work that way as well? You can, as long as you do two things: 1-remember that you're designing for a variable and flexible viewing space, not paper, walls or billboards, and maintain realistic expectations 2-design using tools designed for that purpose. You have to choose tools that accommodate the user interjections that cause problems. You know users can and do use zoom and minimum font size, but when those hit a content space defined in px, the fit disappears. The answer is, don't size content space in px, but instead something that shrinks or grows in direct proportion to the content. Throw away the fixed size measuring stick, and use one that changes with the interjections. Two do that, em, %, though the former is more directly related to content, while the latter relates better to available space. Very simple example: http://fm.no-ip.com/auth/Sites/dlviolin.html Another: http://fm.no-ip.com/auth/Sites/ksc/ More complex examples are provided on http://cssliquid.com/ . Relative sizing is not an easy solution, because it can't be applied to background images, and proportioning of images by existing rendering engines is considerably worse than ideal. But it's certainly better than illegible, missing, overlapping or otherwise broken content. So this is all rather ironic: in order to get things to look right, I have to do them in the wrong way (using px), but in order to do them in the right way (using %), then I'll never be sure that it actually looks right (in fact, I'm virtually guaranteed that things will look wrong for some people). This is the way it has been for years already, since designers were given CSS and px to size web objects with. Then it got worse when browser developers gave users such defenses as text zoom and minimum font size. Those enabled users to enforce text of adequate size to read, but only when the space provided to contain that text was adequate as well. Page zoom can be an improvement, but zoom minimum are user defenses, and they shouldn't be necessary for astute malleable designs. -- Do not let any unwholesome talk come out of your mouths, but only what is helpful for building others up. Ephesians 4:29 NIV 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/
Re: [css-d] Font sizing
At 04:04 PM 2/18/2009 +0100, Gunlaug Sørtun wrote: We web designers create illusions, but there's no reason for us to live in them. Pixel sized text doesn't guarantee the right size anywhere but on our own screen(s) and in our own browser(s), and that's just something all web designers _have to live with_ whether they like it or not. I understand what you're saying, but specifying font sizes in pixels *does* guarantee that things will look *proportionally* the same, regardless of browser/platform. If I specify my font sizes as: 9px, 14px, 23px, 37px, etc. ...then that's what they'll be, no matter what resolution, browser or platform the user is on, and things will all look *proportionally* exactly how I want them. With that said, however, I do understand all the issues with using px instead of percentages (or em) -- but again, this is just my frustration. One day, when the average screen resolution is well above 300dpi, Well, a 300dpi monitor is certainly another reason to *not* go with px, that's for sure! Ron ;) Woof?... http://www.Psymon.com Ach, du Leni!... http://www.Riefenstahl.org Hmm... http://www.Imaginary-Friend.ca __ 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/
Re: [css-d] Font sizing
At 11:39 AM 2/18/2009 -0500, Felix Miata wrote: maintain realistic expectations That much I already learned, many years ago! Are you really really sure? Not really really, just really... ...maybe. Ron ;) __ 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/
Re: [css-d] Font sizing
Ugh. I'm on the verge of just giving up, surrendering defeat, selling my computer, and just making hand-bound books, printed using ink and moveable metal type. It sounds like this is something you have been dealing with for a while, and as someone who works in web and print, and as someone who studies/values fine typography, I can relate. But I think you(the designer) should leave the micromanagement of typographic details to physical media and just try and setup flexible hierarchy and readability in your web designs, as it's (in my opinion) more like software interface design than print design, even though all three share common ancestry and principle. I think when you step into the web world you must surrender the idea of typography being a fine art and see it as a user interface that has some capability to be designed artistically. It's just the nature of the beast, and just as when television was started content was made in a radio format until the true benefits of the platform could be leveraged, web design is still often being looked at as an extension to print design until it's own conventions and philosophies become more prevalent and accepted. It's often very frustrating working for print design studios needing websites for their clients that think that they can manually rag their blocks of text and have it translate to the web, or elegantly justify text... as HJ control is out the window. ~ Joseph __ 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/
Re: [css-d] Font sizing
At 08:57 AM 2/18/2009 -0800, Joseph Sims wrote: It sounds like this is something you have been dealing with for a while, Yes and no, in a way: I suppose I've always been concerned about typographic issues and stuff, but it's really only since I joined this list (last summer) and started taking a closer look at the sites I've created in the past that I began to realize how many issues there are, and how much more I have to learn. All my sites still use tables for layout, for example (please don't shoot me!), and I'm simply just not ready yet, just don't know enough yet, to even consider taking the plunge and changing them all to CSS layouts. Indeed, I feel so ignorant about so much of this stuff that it might well be years before I actually do so -- especially considering that I find myself spending months just trying to figure out the simplest little typographic issues. :/ It's often very frustrating working for print design studios needing websites for their clients that think that they can manually rag their blocks of text and have it translate to the web, or elegantly justify text... as HJ control is out the window. Hey, I have a solution: ALL web sites should be created as PDF files! HTML/CSS be damned! With PDF, everything looks *exactly* how you intended, it's zoomable to any factor you want, and prints out perfectly each time, every time. Phew! We can all relax now... Ron ;) Woof?... http://www.Psymon.com Ach, du Leni!... http://www.Riefenstahl.org Hmm... http://www.Imaginary-Friend.ca __ 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/
Re: [css-d] Font sizing
From: Ron Koster r...@psymon.com Hey, I have a solution: ALL web sites should be created as PDF files! HTML/CSS be damned! With PDF, everything looks *exactly* how you intended, it's zoomable to any factor you want, and prints out perfectly each time, every time. Every frustrated designer new to the (modern) web reaches this conclusion eventually, although at least you didn't suggest one big gif! :-) Of course, you're not being serious, but this does highlight the key difference: PDFs, etc, are fixed layout formats whilst HTML+CSS is flexible. Obviously, some disadvantages come with that flexibility, but the advantages, in particular accessibility, are not to be sniffed at. The trouble with the PDF approach, of course, is that text does not 'reflow' according to zoom level, so you end up having to horizontally scroll at certain font/window sizes, and that makes reading a document painful beyond belief. PDF was never really intended for screen viewing, but as a printable format, which explains this alternative approach. There's possibly an argument here relating to the standard browser behaviour for 'minimum font size'. Browsers currently 'round up' any fonts below that size to the minimum. It would be an interesting alternative approach (possibly configurable) to *scale up all fonts* until they're at least that minimum, so, at least, everything remains in proportion. This would solve your subscript issue but, I fear, could well end up breaking inflexible designs. Either way, it's not really a practical solution just yet, but something to mull over :-) - Bobby __ 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/
Re: [css-d] Font sizing
On Wed, 18 Feb 2009, Ron Koster wrote I understand what you're saying, but specifying font sizes in pixels *does* guarantee that things will look *proportionally* the same, regardless of browser/platform. If I specify my font sizes as: 9px, 14px, 23px, 37px, etc. Not really. There is only a loose relationship between font size and how 'big' text looks on screen. http://www.emdpi.com/fontsize.html -- Richard Mason http://www.emdpi.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/
Re: [css-d] Font sizing
Bobby Jack wrote: From: Ron Koster r...@psymon.com There's possibly an argument here relating to the standard browser behaviour for 'minimum font size'. Browsers currently 'round up' any fonts below that size to the minimum. It would be an interesting alternative approach (possibly configurable) to *scale up all fonts* until they're at least that minimum, so, at least, everything remains in proportion. This would solve your subscript issue but, I fear, could well end up breaking inflexible designs. Either way, it's not really a practical solution just yet, but something to mull over :-) - Bobby An option some flakes :-) employ, from time to time (I'm one of them), is to design the page right from the first second with 200% declared on the body with no other font-size declared throughout the balance of the style sheet. When all is well cross-browser, 200% is reduced to 100%... -- A thin red line and a salmon-color ampersand forthcoming. http://chelseacreekstudio.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/
Re: [css-d] Font sizing [was: Font-color issue]
Ron Koster wrote: At 10:02 AM 2/13/2009 -0800, David Hucklesby wrote: I find that these percentages work best cross-browser: 69%, 75%, 82%, 94% ... with a base font-size of 100%. Firstly, from past threads, my understanding is that one shouldn't be going any smaller than 100% -- or at least should try not to -- if only to be in keeping with whatever it is that any particular user has set their own settings at The 100% is needed as a base to avoid problems in certain browsers - others can explain this in detail far better than I. With regard to respecting users settings it seems more important to create in a way that the text /can/ be scalable to let them do what they want with it - hopefully without breaking your page design. Some ways of sizing prevent this from being possible - or at least make it difficult or problematic. As an avid typophile the following page may be interesting to you. http://www.webtypography.net/Harmony_and_Counterpoint/Size/3.1.1/ regards, Brian __ 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/
Re: [css-d] Font sizing [was: Font-color issue]
At 07:45 PM 2/17/2009 -0600, Brian Funk wrote: The 100% is needed as a base to avoid problems in certain browsers - others can explain this in detail far better than I. With regard to respecting users settings it seems more important to create in a way that the text /can/ be scalable to let them do what they want with it - hopefully without breaking your page design. Some ways of sizing prevent this from being possible - or at least make it difficult or problematic. Well, in that regard, I've been completely re-doing the CSS for my one of my sites (and, in doing so, that will have ultimately have implications across the board for all of my sites), and I've been trying to take the advice that I've gotten here and have set my base font size at 100%, with all my other font sizes done in percentages relative to that (I'm not using em or px anywhere at all, except for in the tiny copyright notice at the bottom of each page). In that regard, the site you pointed out... As an avid typophile the following page may be interesting to you. http://www.webtypography.net/Harmony_and_Counterpoint/Size/3.1.1/ ...brings up exactly what part of my issue is! Firstly, thanks so much for pointing that out -- I'm amazed that I've never come across that site before, and I'll certainly enjoy spending some time there. :) However, it's quite intriguing because Bringhurst's The Elements of Typographic Style -- upon which that site is based -- has largely influenced me (among other sources) with regard to typographic choices. More specifically, his discussion in that book about the Golden Section has had me adopt various font sizes (for headings, etc.) within any particular site by using proportions that fall within that theory/observation of his, and which have made for visually effective and aesthetically pleasing designs. However, the font sizes/proportions/percentages that David mentioned earlier... At 10:02 AM 2/13/2009 -0800, David Hucklesby wrote: I find that these percentages work best cross-browser: 69%, 75%, 82%, 94% ... with a base font-size of 100%. ...have nothing to do with the Golden Section, and to me would look *disproportional* (even if it somehow gets rid of that blur effect that was referred to earlier in the thread) and, well, basically that's why I'm wondering what it is that's going on if/when one uses other, different, in-between percentages. On my system (WinXP) everything looks fine, no matter what browser I'm viewing anything in, and no matter what percentage (or pixel size or whatever else) I'm using for my font sizes. By the way, just to throw another question into the fray, is there anything wrong with using non-whole numbers (like 61.8, etc.) in one's font size percentages? For reference, the closest amounts (to one decimal place) to the percentages that David mentioned that would indeed be perfectly within the Golden Section would be: 61.8%, 76.4%, 85.4% and 94.4%. Those are the sorts of percentages that I'd *like* to use, if I could (without causing problems anywhere/anyhow). Ron :) __ 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/
Re: [css-d] Font sizing
On 2009/02/17 21:59 (GMT-0500) Ron Koster composed: the font sizes/proportions/percentages that David mentioned earlier... At 10:02 AM 2/13/2009 -0800, David Hucklesby wrote: I find that these percentages work best cross-browser: 69%, 75%, 82%, 94% ... with a base font-size of 100%. ...have nothing to do with the Golden Section, and to me would look I have to wonder if more than a tiny fraction of professional web designers know that that is. Probably far fewer of the zillion hack designers or the junkware they use to create would. *disproportional* (even if it somehow gets rid of that blur effect that was referred to earlier in the thread) and, well, basically that's why I'm wondering what it is that's going on if/when one uses other, different, in-between percentages. On my system (WinXP) everything looks fine, no matter what browser I'm viewing anything in, and no matter what percentage (or pixel size or whatever else) I'm using for my font sizes. By the way, just to throw another question into the fray, is there anything wrong with using non-whole numbers (like 61.8, etc.) in one's font size percentages? For reference, the closest amounts (to one decimal place) to the percentages that David mentioned that would indeed be perfectly within the Golden Section would be: 61.8%, 76.4%, 85.4% and 94.4%. Those are the sorts of percentages that I'd *like* to use, if I could (without causing problems anywhere/anyhow). Holy Grail or magic percentages stem from interplay of designers' traditional small (sub-default) fonts fetish, the amount of px each character has to work with, and characteristics of common web fonts. Way back many years ago, typical resolution was really really really low, which produced two significant general effects: 1-fonts with enough px to define them well were really big; 2-the ugliness of inadequate px density seems masked at small sizes. All rendering engines round nominal font sizes to whole numbers of px, but not all browsers use equivalent rounding methods. IE, the dominant overall representative, truncates every computed px size to a whole number, while some popular other browsers use something resembling the mathematical rounding most of us learned when we graduated from simple fractions to decimals in school. When you apply the magic percentages to the sizes available below the traditional 16px default, you find few that land on a whole number. The goal is percentage application that won't result in e.g. 11px in one browser while 12px in others due to their rounding differences, even when one percentage is applied to another through inheritance. To see the comparative differences, visit http://fm.no-ip.com/auth/Font/font-rounding.html in IE, Opera, Gecko Webkit, and compare the differences, and not only at the default font size, but also with different defaults and/or text zoom levels. If you reject the popular designer notion that every page should look identical in every browser, then (presuming you've avoided IE's scaling bugs) a 1px smaller or larger font from one browser to the next should not be a problem. Ultimately, there's a high likelihood that what the user sees will be different anyway, because any of his default text size, screen resolution, display size, seating distance, visual acuity, fonts actually installed, anti-aliasing, minimum font size, zoom level and other factors can vary, thus making it look different. -- Do not let any unwholesome talk come out of your mouths, but only what is helpful for building others up. Ephesians 4:29 NIV 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/
Re: [css-d] Font sizing - Is there a definative method?
Karl Bedingfield wrote: I'm getting confused. There appears to be many ways of font resizing and I cannot make my mind up which is the best method. In the body style some use use 12px and pixel font sizes there after. Some use body style of 100% and percentages there after and finally some use 101% in body with ems there after. Which is the best option for cross-browser performance? Many thanks There is no definitive method. There are numerous theories. Opinions abound. Use the method/theory that best meets your users needs, rather than your need. The 101% (100.01%) as I recall had something to due with a rounding error in Opera (compensation for fonts being a little smaller in that browser). But it is not seen that much in style sheets nowadays. My own opinion is the use of keyword, pixels, em, or percent will all work. Keywords can be problematic, though. Pixels can only be scaled in IE if the user is in accessibility mode with the ignore font-sizes boxed checked (so maybe its not such good idea to use pixels). Em's are fine providing you set a percent base on html, or body declarations, or they'll go totally goofy when scaled (an IE bug). I find using percent throughout the style sheet with line-height set as a raw number (no unit of measure) most consistent /for me/ cross-browser. Typography is a very simple craft whose goal is simply to make words readable. But that ain't easy (particularly on a screen). Honoring user default for the primary content p (user default is medium, 16px, 1em, or 100%) is the way some of us strive to meet that goal. In the end, /it is your call./ -- http://chelseacreekstudio.com/ __ css-discuss [EMAIL PROTECTED] 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/
Re: [css-d] Font sizing - Is there a definative method?
On 2008/07/09 09:46 (GMT-0500) Ben Fider apparently typed: this is a good way to get a consistent font size: * { font-size: 100.01%; /* http://css-discuss.incutio.com/?page=InternetExplorerWinBugs */ } html { /* http://trevordavis.net/blog/tutorial/the-6-most-important-css-techniques-you-need-to-know/ */ font-size: 62.5%; /* will set your font-size to 10 pixels */ } body { font-size:1.2em; /* will set your font-size to 12 pixels */ } One who makes no meaningful attempt to test as visitors actually use their browsers might think so, but the only consistencies that approach brings are: 1-FF2 and Opera users who have a minimum font size set only slightly (~80% or more) or no smaller than their default size, and those with a user stylesheet containing 'body {font-size: 100% !important}', will not see anything remotely resembling what IE, FF3 or Safari users will see. Instead of fonts smaller than their preference as most web sites rudely impose, they'll see fonts _larger_ than their preference. See: http://www.bergamotus.ws/misc/sensible-css-text-sizing.html http://fm.no-ip.com/SS/Clagnut/bbcnSS.html 2-Everyone will be subjected to the rudeness that assuming any main content font size less than 100% of the user's preference (i.e. default) represents. That nearly everyone else is rude is not justification to be rude yourself. See e.g.: http://tobyinkster.co.uk/article/web-fonts/ http://www.w3.org/QA/Tips/font-size http://www.useit.com/alertbox/designmistakes.html http://www.xs4all.nl/~sbpoley/webmatters/fontsize.html http://www.dev-archive.net/articles/font-analogy.html http://fm.no-ip.com/auth/bigdefaults.html http://www.cameratim.com/personal/soapbox/morons-in-webspace -- Do not let the sun go down while you are still angry. Ephesians 4:26 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ __ css-discuss [EMAIL PROTECTED] 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/
Re: [css-d] Font sizing - Is there a definative method?
Thanks for all the help guys, that was very informative :) Karl __ css-discuss [EMAIL PROTECTED] 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/
Re: [css-d] font sizing with decimals as opposed to whole numbers
On 2008/01/15 17:54 (GMT+1300) Michael Adams apparently typed: Can anyone tell me why periodically i come across a site that uses: body { font-size: 100.1%; } That was reputedly to appease ancient Opera versions, around v6 or prior. or: body { font-size: 76.6%; } What browser are they trying to appease here? I don't recall the seeing the .6 tacked onto 76% before, but 76% was Owen Briggs' unfortunate recommendation that a lot of rude designers used and use. http://www.thenoodleincident.com/tutorials/typography/index.html IE ignores the decimals, using 62% if your CSS specifies 62.6%. -- In the beginning was the Word, and the Word was with God, and the Word was God. John 1:1 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ __ css-discuss [EMAIL PROTECTED] 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/
Re: [css-d] font sizing with decimals as opposed to whole numbers
On Tue, 15 Jan 2008 12:21:39 -0500 Felix Miata wrote: On 2008/01/15 17:54 (GMT+1300) Michael Adams apparently typed: Can anyone tell me why periodically i come across a site that uses: body { font-size: 100.1%; } That was reputedly to appease ancient Opera versions, around v6 or prior. THX, time for all to cease and desist it's use. -- Michael All shall be well, and all shall be well, and all manner of things shall be well - Julian of Norwich 1342 - 1416 __ css-discuss [EMAIL PROTECTED] 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/
Re: [css-d] font sizing with decimals as opposed to whole numbers
On Tue, 15 Jan 2008 12:21:39 -0500 Felix Miata wrote: On 2008/01/15 17:54 (GMT+1300) Michael Adams apparently typed: Can anyone tell me why periodically i come across a site that uses: body { font- size: 100.1%; } That was reputedly to appease ancient Opera versions, around v6 or prior. FWIW - My class notes from 2004 blame this on IE6 on Win 98SE. Sadly, I did not note the source for this observation. Cordially, David -- __ css-discuss [EMAIL PROTECTED] 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/
Re: [css-d] Font Sizing: Why Is Firefox Different?
On 06/06/16 14:06 (GMT-0400) Anthony Baker apparently typed: Have been looking to different font sizing methods and decided to go with a method suggested by Dan Cederholm (as I recall) ) Poor choice. Dan Cederholm isn't most people using your designs; he isn't a normal user: http://www.useit.com/alertbox/design_priorities.html . If Dan Cederholm likes small text, he should set his browser so his browser displays text smaller. That's why browsers have a user adjustable preference setting. where the font size is defined in the BODY tag Bad place. There's no good reason to set a size other than 100% (or medium or 1em) in the body rule. 100% is how you respect your visitors, using the size they prefer as your base size, from which you do your contextual sizing with other selectors. When you set some other size in body you're telling your visitors they did something wrong, disagreeing with their preference, which is rude. Everyone's browser defaults are wrong, right? Wrong: http://mrmazda.no-ip.com/auth/bigdefaults.html and then percentages are used to increase or decrease the size. EMs are used for line height. Em for line height is another bad idea. It really serves no good purpose, and should either be removed from the CSS3 spec, or its definition altered. http://mrmazda.no-ip.com/auth/line-height-inherit.html shows why. Example of the base setting: body {font-size: small;} This has worked fine across Safari and IE browsers and should work on Firefox, but I've noticed that there's a distinct difference in the way Firefox is rendering text -- both on the Mac and on IE. Maybe you see the result of a settings difference. Are you using a laptop? What's your DPI set to? The base size in most browsers is DPI dependant, with the user preference size set in pt. Firefox isn't, with preference set in px. Does anyone know why this happens when IE and Safari work so well? It may be a small issue, but damned if it isn't annoying. Overall, font sizes seem smaller and line spacing tighter. In which? How about screenshots showing us exactly what you see that bothers you? NAICT, Safari FF are a match. Even on a site like the NY Times, this sort of thing seems to be happening here and there -- particularly in the text of the body of an article. Various browsers have differing rounding methods. Various font subsystems calculate leading slightly differently. Couple those differing methods with the differences in the way various font families scale, and you're insured against everything always looking the same in every browser. Take a look at http://mrmazda.no-ip.com/auth/Font/font-rounding.html in all your browsers and it is clear they don't all round the same. Generally, IE truncates (but not always), while Gecko uses mathematical rounding (often poorly - see https://bugzilla.mozilla.org/show_bug.cgi?id=177805). See also: http://lists.css-discuss.org/mailman/private/css-d/2006-May/064598.html Does anyone have a favorite method? body {font-size: 100%} (or just nothing, saving a dozen bytes per load). Would love to get something that's accessible and as consistent as possible. Accessible means you don't create artificial visitor difficulty by applying arbitrary adjustments to text size in body. small in body applies a size reduction from user preferred size to every letter you don't change elsewhere, resulting in increased reading difficulty, and thus decreased accessibility. Plus, it shows disrespect of your visitors. -- All have sinned fall short of the glory of God. Romans 3:23 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font Sizing: Why Is Firefox Different?
On 6/16/06, Anthony Baker [EMAIL PROTECTED] wrote: Have been looking to different font sizing methods and decided to go with a method suggested by Dan Cederholm (as I recall) )where the font size is defined in the BODY tag and then percentages are used to increase or decrease the size. EMs are used for line height. Example of the base setting: body { font-family: Arial, sans-serif; font-size: small; } I'm coming more and more to the view that we should, as much as reasonable, honor the user's preferences. I'd therefore change your rule slightly to make the default font-size on the body either 1em, 100%, or medium, all of which I believe are equivalent and display text at the browser's default font size. Or just leave it out, which amounts to the same thing. With Geko based browsers (Netscape, Firefox, and many others) the user can resize his fonts with a keystroke, so really, what's the point of fighting? I try to design my your sites so that they look OK in just about any font size or screen resolution. That means giving up the idea that I actually have any control over the user's preferences. Fact is I don't and neither does anybody else. And doing things that way makes things a lot easier but still leaves a surprising amount of room for creativity in page design. Of course what works for me may not work for anybody else. -- Ed Seedhouse __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font Sizing: Why Is Firefox Different?
Anthony Baker wrote: Have been looking to different font sizing methods and decided to go with a method suggested by Dan Cederholm (as I recall) )where the font size is defined in the BODY tag and then percentages are used to increase or decrease the size. EMs are used for line height. Fine, but avoid that 'font-size: 62.5%' or 'small' on body - unless you like to have your fonts blown up to a really big size when subjected to 'minimum font size' in Firefox and Opera. For more on the subject: http://www.gunlaug.no/contents/wd_1_03_04.html Example of the base setting: body { font-family: Arial, sans-serif; font-size: small; } This has worked fine across Safari and IE browsers and should work on Firefox, but I've noticed that there's a distinct difference in the way Firefox is rendering text -- both on the Mac and on IE. 1: check 'minimum font size', since Firefox and Safari apply it differently, as mentioned in my article. Not much you can do about it if you use small font-size on body, since that means body has 11pt (14px) font-size at _my_ end. Does anyone know why this happens when IE and Safari work so well? It may be a small issue, but damned if it isn't annoying. Overall, font sizes seem smaller and line spacing tighter. 2: There are slightly different tip-over points for font-sizes in different browsers. You'll have to figure out the average values that'll work across browser-land if you want consistency - or else you'll get +/- 1px variations. Even on a site like the NY Times, this sort of thing seems to be happening here and there -- particularly in the text of the body of an article. Does anyone have a favorite method? Yes :-) - I size fonts based on normal (12pt (16px)) - or not at all. - I select average font-size values, and test across browser-land. - I blow everything up in all browsers, and make sure it doesn't break too badly at twice the normal font-size. - I leave the rest to the visitor. Would love to get something that's accessible and as consistent as possible. Accessible is what the visitor can access/read at their end. That has nothing to do with font-size consistency. Try out IE/win's accessibility mode -- ignore font sizes for size. That option is all about accessibility and cross-site consistency. regards Georg -- http://www.gunlaug.no __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font Sizing: Why Is Firefox Different?
On 6/16/06, Anthony Baker [EMAIL PROTECTED] wrote: Hey Folks, Am wondering if someone has any info on this for me. Have been looking to different font sizing methods ... Does anyone have a favorite method? I'll give you my favorite, which seems to work allright. html { font-size:100.01%; /* fixes some browser bugs */ } body { font-size:1em; /* always */ } optional: #container { font-size:.9em; /* if I must */ } everything thereafter is in em. I avoid hundredths (.95 for example) because browsers round ems to a pixel size and hundredths can round differently in different browsers. Tenths are a little more predictable. And I guess you could use percents just as well as ems, but I like ems. and yes, I think I have seen that starting with font-size:small can have problems in certain browsers, so there you go. -- -- Christian Montoya christianmontoya.com ... portfolio.christianmontoya.com __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font Sizing: Why Is Firefox Different?
Have you ever tried using ems for font-sizing? I've always had very good luck with cross-browser compatability if I set my font sizes in ems. 1em is = 12px font, while .8em is equivalent to 10px. The code is simply: font-size: .8em; __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font Sizing: Why Is Firefox Different?
Anthony Baker wrote: Am wondering if someone has any info on this for me. I think you have entered the twilight zone of personal opinion :-P . Not to mention font wars that some of us love, but are a no/no on this list. There are numerous pages on font-sizing in the list wiki. If you want a personal opinion, write *off-list.* Thanks, Anthony Best, ~dL __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] Font Sizing: Why Is Firefox Different?
On 06/06/16 14:49 (GMT-0400) Jade Rauenzahn apparently typed: I've always had very good luck with cross-browser compatability if I set my font sizes in ems. 1em is = 12px font, while .8em is equivalent to 10px. In most browsers, 'html, body {font-size: 1em}' produces 12pt text, not 12px text. With the most common browser/system DPI (96), 12pt is 16px. .8 X 12pt is 9.6pt (12.8px), not 10pt, which different browsers variously may round either to 12px (truncation) or 13px (mathematical rounding). -- All have sinned fall short of the glory of God. Romans 3:23 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
font-size / line-height http://www.w3schools.com/css/pr_font_font.asp Shawn what is the intent of the size calculation 62.5%/1.6em? -nick __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
On 06/05/23 11:15 (GMT-0400) Nick Lehman apparently typed: I came across this while trolling through someone's css file: body { font: 62.5%/1.6em ...} what is the intent of the size calculation 62.5%/1.6em? That 62.5% hocus pocus CSS is for designers who think px are more important than visitor respect and content fluidity. It originated and is explained here: http://www.clagnut.com/blog/348/ See also re the line-height: http://mrmazda.no-ip.com/auth/line-height-inherit.html http://www.w3.org/TR/CSS21/fonts.html#font-size-props -- All have sinned fall short of the glory of God. Romans 3:23 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
On 5/23/06, Shawn Lawler [EMAIL PROTECTED] wrote: what is the intent of the size calculation 62.5%/1.6em? Felix? :-) -- Tom Livingston Senior Multimedia Artist Media Logic www.mlinc.com __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
ahh...it's not math it's a separator. Thanks On May 23, 2006, at 11:25 AM, Shawn Lawler wrote: font-size / line-height http://www.w3schools.com/css/pr_font_font.asp Shawn what is the intent of the size calculation 62.5%/1.6em? __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
what is the intent of the size calculation 62.5%/1.6em? -nick Basically the general browser default size is 16px so 62.5% gives a text size of 10px. That means 1em = 10 pixels so pixel dimensions can be converted into ems so the layout will scale according to text sixe. The em measurement after the slash refers to line-height. -- http://www.web-buddha.co.uk dynamic web programming from Reigate, Surrey UK (php, mysql, xhtml, css) look out for project karma, our new venture, coming soon! __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
Just to clarify Nick, the 62.5%/1.6em isn't a calculation as in 62.5% divided by 1.6em. It is shorthand for font-size/line-height. In this case, the 62.5% sets the font-size to a percentage of the browser's default font-size. The 1.6em does something similar but uses the em unit which like percentage is used for relative sizing rather than px, pt and pc units. Hope this helps. K __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
Felix Miata wrote: That 62.5% hocus pocus CSS is for designers who think px are more important than visitor respect and content fluidity. It originated and is explained here: http://www.clagnut.com/blog/348/ It's also broken on IE-Win, which ignores the decimal fraction of percentages on the font-size. Thus it treats the above as font-size: 62%; giving a font-size of 9.92px. If you then try to specify the dimensions of something in ems, it comes out smaller on IE than everything else. For example, width: 40em; will give a width of 400px on FF, Opera, Safari etc. (assuming default font size settings), but of 396px on IE. This can be the cause of much frustration when creating em-based layouts. I'm planning to write this up in detail (as workarounds can fall foul of a user's minimum font size if one doesn't take them into account) but for the moment I've got a demo here: http://www.nickfitz.co.uk/bugs/browsers/css/IE-Win/ie_percent_test.html HTH, Nick. -- Nick Fitzsimons http://www.nickfitz.co.uk/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
Nick Lehman wrote: I came across this while trolling through someone's css file: body { font: 62.5%/1.6em Lucida Grande, Arial, Verdana, sans-serif; color: #000; background-color: #FFF; } what is the intent of the size calculation 62.5%/1.6em? -nick It is the font and line-height specification, /some/ might say, by an author who is a control freak: 62.5% is the authors font-size preference(in other words, the author is specifying her desire to reset the users font-size preference 37.5% /smaller/ than the user prefers). And 1.6em is the authors line-height(leading) preference(in other words, the author is specifying her desire to reset the users line-height preference .3em or .4em /greater/ than the user prefers). Default is font: 100%/1.2 (or 1.1) sans-serif; (line-height is expressed as a raw number, and does not carry a unit of measure such as px, em, or percent). HTH ~davidLaakso PS The above is my personal opinion and it not shared by all on this or any other list. -- http://www.dlaakso.com/gustave/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
Re: [css-d] font sizing
On 06/05/23 13:07 (GMT-0400) Nick Fitzsimons apparently typed: It's also broken on IE-Win, which ignores the decimal fraction of percentages on the font-size. Thus it treats [62.5%] as font-size: 62%; giving a font-size of 9.92px. If you then try to specify the dimensions of something in ems, it comes out smaller on IE than everything else. For example, width: 40em; will give a width of 400px on FF, Opera, Safari etc. (assuming default font size settings), but of 396px on IE. This can be the cause of much frustration when creating em-based layouts. I'm planning to write this up in detail (as workarounds can fall foul of a user's minimum font size if one doesn't take them into account) but for the moment I've got a demo here: http://www.nickfitz.co.uk/bugs/browsers/css/IE-Win/ie_percent_test.html Look at http://mrmazda.no-ip.com/auth/Font/font-rounding.html and see Opera 9, KHTML, IE, and Gecko all match to 3 decimal places for pt sizes, but there's a dichotomy between Gecko/KHTML and IE/Opera on fractional px. If limited to M$, check KHTML at: http://www.snugtech.com/safaritest/ -- All have sinned fall short of the glory of God. Romans 3:23 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://mrmazda.no-ip.com/ __ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/