W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: LONGDESC: some current problems and a proposed solution added to the wiki

From: Bill Mason <w3c@accessibleinter.net>
Date: Sat, 30 Jun 2007 21:14:53 -0700
Message-ID: <46872A3D.80903@accessibleinter.net>
To: Sander Tekelenburg <st@isoc.nl>
CC: public-html@w3.org

Sander Tekelenburg wrote:
> At 12:44 -0700 UTC, on 2007-06-30, Bill Mason wrote:
> 
>> Sander Tekelenburg wrote:
> 
> [...]
> 
>>> Test case at <http://santek.no-ip.org/~st/tests/longdesc/>. [...]
>> In Netscape 6.2 and 7.0 (Macintosh), the longdesc URL is a clickable
>> link in the image properties window.  The link opens in the same window,
>> with no other visual indicators once the page loads.
> 
> Thanks.
> 
> Are you saying Netscape ignores the fragment identifier; it doesn't scroll to
> the anchor?

No, it does scroll to the anchor.

> To be clear, where on <http://santek.no-ip.org/~st/tests/longdesc/> I say
> "iCab [...] indicates the anchor" I didn't mean to imply that this has
> anything to do with its longdesc implementation. iCab always indicates an
> anchor when you follow a URL with a fragment identifier. It does, because the
> usual UA behaviour of merely scrolling there[*] doesn't work if the anchor is
> at the bottom of a page.

That's what I didn't realize when I wrote my description.  I thought it 
was an indicator specific to longdesc.

-- 
Bill Mason
Accessible Internet
w3c@accessibleinter.net
http://accessibleinter.net/
Received on Sunday, 1 July 2007 04:15:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT