ISSUE-214: Handling of Meta Refresh

Handling of Meta Refresh

State:
CLOSED
Product:
mobileOK checker
Raised by:
Jo Rabin
Opened on:
2007-09-04
Description:
The question is, should we stop on meta refresh (because we may be testing a page the user never sees, or should we test the page anyway, as if the timeout is long enough, they will in fact see it).

Where does warning the user that the results may not refer to the page they tohout they were testing fit in to all this?

Should we actually follow Meta redirects, contrary to our religion?

Related Actions Items:
No related actions
Related emails:
  1. [minutes] Thursday 27 March 2008 Teleconf (from fd@w3.org on 2008-03-27)
  2. [minutes] F2F Meeting Day 2 - 6 November 2007 (TPAC) (from dom@w3.org on 2007-11-12)
  3. Re: ISSUE-214: Handling of Meta Refresh [mobileOK Basic tests] (from atrasatti@mtld.mobi on 2007-09-14)
  4. [minutes] Checker F2F Day 1 (Sep 4) (from dom@w3.org on 2007-09-05)
  5. RE: ISSUE-214: Handling of Meta Refresh [mobileOK Basic tests] (from k.scheppe@t-online.net on 2007-09-04)
  6. ISSUE-214: Handling of Meta Refresh [mobileOK Basic tests] (from sysbot+tracker@w3.org on 2007-09-04)

Related notes:

moved to bugzilla: http://www.w3.org/Bugs/Public/show_bug.cgi?id=5591

Dominique Hazaël-Massieux, 27 Mar 2008, 16:18:46

Display change log ATOM feed


Jo Rabin <jo@linguafranca.org>, Daniel Appelquist <daniel.appelquist@vodafone.com>, Chairs, Dominique Hazaël-Massieux <dom@w3.org>, François Daoust <fd@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 214.html,v 1.1 2011/01/10 15:19:43 dom Exp $