Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id C64F36345E7 for ; Tue, 31 Aug 2010 13:28:16 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 75599-01-10 for ; Tue, 31 Aug 2010 16:28:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id E0C80635D86 for ; Tue, 31 Aug 2010 13:14:35 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o7VGEWdx004393; Tue, 31 Aug 2010 12:14:32 -0400 (EDT) To: Thom Brown cc: Kevin Grittner , Dave Page , pgsql-docs@postgresql.org, Erik Rijkers Subject: Re: [pgsql-www] Example indenting In-reply-to: References: <4C7558140200002500034BE5@gw.wicourts.gov> <1282778956.11634.585.camel@jd-desktop.unknown.charter.com> <4C760112.807@lelarge.info> <1282842211.17406.6.camel@jd-desktop.unknown.charter.com> <4C765CB60200002500034C39@gw.wicourts.gov> <1282844645.17406.10.camel@jd-desktop.unknown.charter.com> <4C7797830200002500034D17@gw.wicourts.gov> <4C779D190200002500034D25@gw.wicourts.gov> <4C7A320D0200002500034DAE@gw.wico! urts.gov> <18772.1283099286@sss.pgh{ h@ T Comments: In-reply-to Thom Brown message dated "Tue, 31 Aug 2010 17:09:12 +0100" Date: Tue, 31 Aug 2010 12:14:32 -0400 Message-ID: <4392.1283271272@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201008/150 X-Sequence-Number: 5974 Thom Brown writes: > Well that was a pain. Didn't realise there was a special hacky CSS > file to fix fonts for gecko and webkit browsers. We use javascript to > add it in on the current documentation, which is a nasty hack (try > disabling javascript and look at our docs in Firefox, Chrome or > Safari... the monospace text will be really small). Fortunately I've > worked around that, with the downside being that if users have > selected different default font settings for their browser, I've > overridden it. Now the font sizes should be virtually the same in all > browsers. That seems pretty unfriendly from an accessibility standpoint. regards, tom lane