X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
From:	Adam Dinwoodie <Adam DOT Dinwoodie AT metaswitch DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	RE: One unreadable sentence at http://cygwin.com/setup.html
Date:	Fri, 8 Feb 2013 14:19:19 +0000
Deferred-Delivery:	Fri, 8 Feb 2013 14:19:00 +0000
Message-ID:	<CE9C056E12502146A72FD81290379E9A608E3622@ENFIRHMBX1.datcon.co.uk>
References:	<20130208021109 DOT GA19883 AT nt1 DOT in> <575434823 DOT 20130208141302 AT mtu-net DOT ru> <5114D3E6 DOT 2030107 AT towo DOT net> <CE9C056E12502146A72FD81290379E9A608E33AD AT ENFIRHMBX1 DOT datcon DOT co DOT uk> <20130208120428 DOT GB6512 AT calimero DOT vinschen DOT de> <5114EFC6 DOT 2050605 AT towo DOT net> <20130208130305 DOT GC6512 AT calimero DOT vinschen DOT de>
In-Reply-To:	<20130208130305.GC6512@calimero.vinschen.de>
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id r18EJbLM009249

Corinna Vinschen wrote:
> On Feb  8 13:29, Thomas Wolff wrote:
>> Am 08.02.2013 13:04, schrieb Corinna Vinschen:
>>>What would be the right fix?
>> Very weird; I can't reproduce the issue right now. When I checked
>> earlier, though, the issue was affected by the line I quoted
>> (shouldn't be, indeed, maybe a bug in Firefox) while the ".3em" line
>> does not exist in the style sheet.
>> I suggest to just remove the dot before "1em" in the "#navbar h4"
>> style, whatever its purpose might be...
>
> Done.  Can you please check if that fixed the OPs problem?

Fixed on my Google Chrome.

Although I'd argue the correct fix would be to replace the <h4>...</h4> with
<p><strong>...</strong></p>.  That makes more semantic sense to me, since that
line isn't really a header at all.

-- 
Adam Dinwoodie

Messages posted to this list are made in a personal capacity.

- Raw text -