W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2002

RE: whitespace, navigation links, styled divs

From: Steve Vosloo <stevenvosloo@yahoo.com>
Date: Mon, 12 Aug 2002 21:26:53 +0200
To: <w3c-wai-ig@w3.org>
Message-ID: <005c01c24236$3b9a2460$b1e91ec4@theijunction.icelogic.co.za>

If we can't use the invisible chars to separate links with more than
whitespace, what can we do?

Steve





-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
Behalf Of Julian
Sent: 10 August 2002 12:59 PM
To: w3c-wai-ig@w3.org
Subject: Re: whitespace, navigation links, styled divs



> For a truly CSS compliant renderer, that is the same as if the span 
> element didn't exist at all.

..and for users with both a truly css compliant browser and a
screenreader the span wouldn't appear and the links would run together.
Good point David and I shall stop doing it.

>I think you are abusing display:none to
> take advantage of bugs in it's implemnetation,

What's wrong with that? In principle I mean, not in relation to this
particular example which I concede is bad practice.

Julian

----- Original Message -----
From: "David Woolley" <david@djwhome.demon.co.uk>
To: <w3c-wai-ig@w3.org>
Sent: Friday, August 09, 2002 10:05 PM
Subject: Re: whitespace, navigation links, styled divs


>
> > I have done something similar to that; put a "." in a span after 
> > each
link
> > and style it to display:none. I don't think this causes any problems

> > for
>
> For a truly CSS compliant renderer, that is the same as if the span 
> element didn't exist at all.  I think you are abusing display:none to 
> take advantage of bugs in it's implemnetation, or a correlation 
> between browser that don't distinguish adjacent links and ones that 
> don't support CSS2.
>
Received on Monday, 12 August 2002 15:24:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:05 GMT