Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 31DE09FA434 for ; Sun, 7 Jan 2007 13:26:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 14434-06 for ; Sun, 7 Jan 2007 13:26:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 76DE99FB1BB for ; Sun, 7 Jan 2007 13:26:37 -0400 (AST) Received: from [192.168.199.198] (c213-100-160-41.swipnet.se [213.100.160.41]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by svr2.hagander.net (Postfix) with ESMTP id 97972DCC121; Sun, 7 Jan 2007 18:26:36 +0100 (CET) Message-ID: <45A12D56.8040809@hagander.net> Date: Sun, 07 Jan 2007 18:26:46 +0100 From: Magnus Hagander User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Robert Treat CC: pgsql-www@postgresql.org, Tom Lane , perrym3@gmail.com Subject: Re: Patch for text.css References: <20070106173601.E08E5DCC11C@svr2.hagander.net> <4387.1168105682@sss.pgh.pa.us> <200701062237.01030.xzilla@users.sourceforge.net> In-Reply-To: <200701062237.01030.xzilla@users.sourceforge.net> X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/11 X-Sequence-Number: 11278 Robert Treat wrote: > On Saturday 06 January 2007 12:48, Tom Lane wrote: >> "Magnus Hagander" writes: >>> in principle i like it, but there was a reason it was there. anyond know >>> why? Objections to changing it1? >> Surely it was just a typo --- I can't believe anyone would intentionally >> hide the difference between visited and unvisited links. The question >> though is what two colors we want to use. >> > > I'd be more surprised if it wasn't done intentionally; web designers use this > technique all the time, claiming it adds a more consitent color scheme / look > to the website. Usability analysts will tell you that anything you think you > gain in asthetics is lost in breaking the standard color conventions people > are used to. The above patch sets visited links as a darker/paler blue; if we > are going to change it I'd suggest going with the standard purple color (or > something very similar). Or should we perhaps just stop setting a color at all on it? That would let the browser choose color? I don't know how common it is for people to change the colors of the links, but I'm sure some do... And then we'd just go with whatever the browser had? //Magnus