W3C home > Mailing lists > Public > www-validator@w3.org > February 2002

Re: opening a link in a new window: is it really so bad?

From: Allan Clark <allanc@caldera.com>
Date: Fri, 22 Feb 2002 16:16:41 -0500
Message-ID: <3C76B539.5F5F9498@caldera.com>
To: todd fahrner <fahrner@pobox.com>
CC: www-validator@w3.org
> >   There's no reliable method that
> > provides reliable fallback without the target attribute, and the
> > failure
> > scenarios are IMO serious enough that you just can't do it.  Still if
> > it's not in standard, it's surely not there for a reason,
> > subverting that
> > with script just can't be sensible.
> 
> I think you are too ready to ascribe godlike qualities to human
> spec/guideline authors.

If the spec does indeed turn out to be too restrictive, we may have to
change it.  Is there anyone on this feed who can go about recommending
an ammendment to the script?

I think this yellow-brick-road started with <A HREF=".." TARGET="..">. 
Clearly, the ability to target another window by name is a neat trick,
and helps make pages that navigate well, without the need for activating
script interpreters on a browser.  

The point I'm trying to make is that this may be a useful addition to
the spec, since it allows links to affect other windows in a lightweight
browser that has no scripting.  Granted, this should be "with the
permission of the user", but in a data element such as <A ...TARGET=..>
the browser can recognize this and perhaps check permissions to see if
this is permitted.

It's clearly possible that the spec writers tried to get away from this
kind of trick, but this particular trick remains very useful and
light-weight.

Allan
Received on Friday, 22 February 2002 16:15:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 April 2012 12:14:00 GMT