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

Re: New Window inform

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 9 Aug 2002 12:02:59 -0400 (EDT)
To: David Woolley <david@djwhome.demon.co.uk>
cc: <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.30.0208091159260.21800-100000@tux.w3.org>

No, but the point Kynn made is that you can do this in your user style sheet
and apply it to your browser. If people had CSS2 capable browsers as a matter
of course (after all, it is only about 5 years since the specification was
published as a W3C Recommendation) then we could provide this user style
sheet rule and not worry any more about whether the author put it in content.

Where people are relying on pictures, and getting confused by new windows
opening, a different approach is probably smarter - I would suggest the
feature that many browsers have of forcing pages to open in the existing
window, and keeping the history. (iCab does a slightly different thing - you
can normally go back in the new window to the page from which you opened it,
but not before. Opera gives you a more powerful history again as I recall).



On Thu, 8 Aug 2002, David Woolley wrote:

>>       a[target="_new"]:after { content: "(This will open in a new window.)"; }
>Is generated content considered part of the element?  If not, or ambiguous,
>this may not get read if one is just skipping through the links.
>There's also the problem of people who rely on pictures rather than text.

Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI  fax: +33 4 92 38 78 22
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Friday, 9 August 2002 12:03:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:10 UTC