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

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

From: Jim Ley <jim@jibbering.com>
Date: Tue, 15 Jan 2002 15:13:47 -0000
Message-ID: <013601c19dd7$3b576fc0$ca969dc3@emedia.co.uk>
To: <w3c-wai-ig@w3.org>
"Jon Hanna"
> > Surely though any content in a popup or spawned window is
> > innaccesbile to those browsers which have turned off spawned
> > windows?
>
> function safePopUp(){
> try{
> popUpFunc()
> return false
> }
> catch(e){
> return true
> }
> }

Is this supposed to be ECMAcript?  You know that you can't use try and
catch in javascript on webpages as browsers fully compliant to the
ECMAScript standard do not understand it and generate script syntax
errors upon encountering it?  Equally window.open does not currently
throw an error where it's blocked (as that would be just as
disorientating/annoying as having the window open.) it's silently
ignored, so whilst your code might help AvantGo (the only ECMAScript Ed.3
browser I can think of where window.open throws an error.) it doesn't
solve the problem, indeed it makes it worse.  There is a method for doing
what you want (see below) but I struggle to see how a normal link can be
a happy fallback situation as if that's okay - why aren't you using it
anyway?

<a href="chicken.html" target="chicken" onclick="if (window.open)
window.open('','chicken')">

Jim.
Received on Tuesday, 15 January 2002 10:15:30 GMT

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