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

RE: on the future: was: Re: forms problem

From: Jon Hanna <jon@spinsol.com>
Date: Tue, 15 Jan 2002 15:01:24 -0000
To: <w3c-wai-ig@w3.org>
Message-ID: <NDBBLCBLIMDOPKMOPHLHGENADLAA.jon@spinsol.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Surely though any content in a popup or spawned window is
> innaccesbile to those browsers which have turned off spawned
> windows?

<a href="blah.html" target="_blank">link</a> will open in a new
window when frames are available, but if frames aren't available it
will open in an appropriate manner.

<a href="#" onclick="popUpFunc();">link</a> will break if frames
and/or script aren't available, however:

function safePopUp(){
	try{
		popUpFunc()
		return false
	}
	catch(e){
		return true
	}
}
...
<a href="blah.html" target="_blank" onclick="return
safePopUp();">link</a> has the following possibilities:

If scripts and frames are available then popUpFunc will be called
(presumably displaying a pop-up window) and all is well.

If scripts aren't available but frames are then blah.html will be
loaded into a new window, and all is well.

If neither are available blah.html will be loaded in an appropriate
way, and all is well.

If scripts are available but frames aren't then either popUpFunc will
display blah.html appropriately (window.open may be defined by the
browser to do so) or it will error (perhaps compaining than
window.open doesn't exist or has been disabled), the error will be
caught and true will be returned, causing the default link behaviour
to load blah.html in an appropriate way, and all is well.

Therefore it is easy to code for situations where users opt to turn
off pop-ups.

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBPEREP4Fpv9f1Mr0YEQKruQCg6aAcaU2Y/JJ6TWBLE2DaF+QzlI4AoIAa
ZnJx7yLgWVNZgt3kB4a81YSG
=RqA9
-----END PGP SIGNATURE-----
Received on Tuesday, 15 January 2002 10:02:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:00 GMT