W3C home > Mailing lists > Public > public-html@w3.org > November 2008

Re: a/@ping discussion (ISSUE-1 and ISSUE-2), was: An HTML language specification vs. a browser specification

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 24 Nov 2008 15:44:47 -0800
Message-Id: <D5CFCC6A-AB5D-4C5C-AFB2-6599A04A7AB2@apple.com>
Cc: Ian Hickson <ian@hixie.ch>, "Roy T. Fielding" <fielding@gbiv.com>, HTML WG <public-html@w3.org>
To: Julian Reschke <julian.reschke@gmx.de>

On Nov 24, 2008, at 2:59 PM, Julian Reschke wrote:

>>> Not displaying the target of a link is considered a security  
>>> issue nowadays. I hope that at some point some of the specs we're  
>>> working on will have a Security Considerations section pointing  
>>> that out.
>>> The point I was trying to make was that one of the "four big" UAs  
>>> doesn't even get *this* right, so I have my doubts that the  
>>> situation will be any better with a/@ping.
>> I tried all my browsers and couldn't find one that didn't show the  
>> URL when hovering over a link, so I'm not sure what you're  
>> referring to here. If we get as good interop with ping="" as with  
>> <a href="">, I'll be happy.
> At least on Windows XP, Safari does not display the link target  
> anywhere.

Safari displays the target URL of a hovered link in the status bar,  
which is off by default, but easy to turn on.

Received on Monday, 24 November 2008 23:45:19 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:39 UTC