ISSUE-132: AUTO_REFRESH and REDIRECTION

AUTO_REFRESH and REDIRECTION

State:

CLOSED

Product:

mobileOK Basic tests

Raised by:

Jo Rabin

Opened on:

2006-08-31

Description:

Two points on this one.

First that if the page is found to have a refresh then there should be a WARN
not a FAIL, because the Best Practice says that you can have refreshing pages as
long as you allow the user a way out.

Second - surely if we are testing for <meta http-equiv=\'refresh\'/> we should
also test the http headers for refresh too? Though, interestingly (well,
relatively so), the Refresh header is not actually part of HTTP 1.0 or 1.1. So
ref ISSUE-130 the DDC needs to be defined as supporting HTTP 1.0 plus refresh
(or not, whatever the group decides).

Related Actions Items:

No related actions

Related emails:

1. mobileOK Basic Tests Version 1n (from jo@linguafranca.org on 2006-10-06)
2. [minutes] Summary of our Gijon F2F (from dom@w3.org on 2006-10-04)
3. ACTION-325 Prepare a response to Nokia\'s feedback - [Part 2 response to MOK doc comments] (from jo@linguafranca.org on 2006-09-14)
4. RE: ISSUE-132: AUTO_REFRESH and REDIRECTION (from jo@linguafranca.org on 2006-09-04)
5. RE: ISSUE-132: AUTO_REFRESH and REDIRECTION (from dom@w3.org on 2006-09-04)
6. Re: ISSUE-132: AUTO_REFRESH and REDIRECTION (from srowen@google.com on 2006-09-01)
7. ISSUE-132: AUTO_REFRESH and REDIRECTION (from dean+cgi@w3.org on 2006-08-31)
8. Re: ISSUE-132: AUTO_REFRESH and REDIRECTION (from dom@w3.org on 2006-08-31)

Related notes:

No additional notes.

Display change log