Re: [css3-hyperlinks] Comments about the New Draft


> The 'target-name' property
>    Except for 'current', the other properties may cause unexpected
> actions such as opening a new window/tab and replacing a frameset.
> Therefore, I think it should be stated that the UA SHOULD/MUST make the
>   action known to the user, through a UA specific means, prior to
> activation.

I do not agree that user agents should or must provide notifications for
target-name property values other than "current"; such notifications could
be very disruptive in innocuous page designs.  Consider a page that has
another page embedded via an object element with the embedded page serving
as a content menu (an arrangement that results in having accessible content
without sacrificing usability).  By using the "target-name" property for
link "styles", the content publisher could specify whether a content link
should open within the object element (for a resorted or respecified content
list, for example) or at the root of the current document hierarchy.  If a
confirmation window pops up each time the user clicks on a root link, such a
usable arrangement would become tedious.

And what if a Web developer wants to target all local links at the root of
the document hierarchy to escape framesets from other domains?

It may be preferable for security and annoyance notifications to be
implemented at the discretion of user agent developers.

I am not a security expert, but here is an example of a user agent option to
prevent security issues that may arise from link targets (such as spoofing
other Web sites):

[ ] Warn me when following a link that is targeted at a different frame,
tab, window, etc.

    [ ] Unless the linked page is within the same domain.

Here is an example of a user agent option to prevent the annoying habit some
Web developers have of opening all off-site links in new windows:

Open links that are targeted at new/blank windows...

    ( ) in a new window (as targeted).

    ( ) at the root of the current document hierarchy (like "_top"; this
would be compatible with tabs, etc. without requiring one to specify tab,
window, etc.).

    ( ) in a new tab (or slide, etc.).

A preference prompt could be displayed the first time a link targeting a new
window is detected by a user agent then stored (and, of course, editable via
a configuration panel later) so users would not need to edit their user
style files manually.

Kind regards,

Brian Sexton

Received on Wednesday, 19 May 2004 02:36:34 UTC