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

Client-Side Redirects Using HTTP-EQUIV="refresh"

From: Matt Nuttall/CanWest/IBM <mnuttall@ca.ibm.com>
Date: Mon, 21 Jan 2002 18:11:17 -0500 (EST)
To: w3c-wai-ua@w3.org
Message-ID: <OF4EB64D03.6F85E11D-ON08256B48.007E3573@mkm.can.ibm.com>
Hi Folks;
     Sorry to be bothering you with this question, but
I've been looking for a solution to a condition related to
your Client-Side Redirects Using HTTP-EQUIV="refresh"
checkpoint 3.6.
     Here is my problem: I use HTTP-EQUIV refresh
constantly to refresh a page for an internal company
website.  Since some of these users are half the world
away, network delays/problems can cause the refresh
to fail.
     Here is my question: what mechanism exists
to give the client control over the failure to refresh?
Preferably so that a JavaScript alert window could be
opened to inform the client via pop-up window that the
refresh has failed.
Thanks for your time and my apologies if this question
is inappropriate.

Matthew E. Nuttall

IBM Global Services
4601 Canada Way
Burnaby, BC  V5G 4X3
phone: 604-297-2336    fax: 604-297-2800
mnuttall@ca.ibm.com
Received on Tuesday, 22 January 2002 01:12:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:03 GMT