This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 829 - Follow <meta http-equiv="refresh" ...
Summary: Follow <meta http-equiv="refresh" ...
Status: NEW
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.0
Hardware: Other other
: P2 enhancement
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
Depends on:
Reported: 2004-07-24 13:29 UTC by Bj
Modified: 2007-03-29 18:48 UTC (History)
0 users

See Also:


Description Bj 2004-07-24 13:29:28 UTC
The Validator should be able to follow <meta http-equiv="refresh" ...> to ease 
batch validation for many pages with unknown content.
Comment 1 Terje Bless 2004-08-05 08:14:38 UTC
Leaving aside my distaste for <meta> hacks for a moment...

In what way will this ease "batch validation" and what's the relevance of "unknown content" to the issue?
Comment 2 Bj 2004-08-05 17:50:37 UTC
E.g. for I am not interested how valid 
the redirection pages the document links to are, but rather how valid the final 
destination is. Is that not obvious?
Comment 3 David Dorward 2004-08-06 02:41:05 UTC
I don't see a <meta> refresh on that document.

While you might not care if a redirecting page is valid or not, others could
well be. If for some reason I were to use a meta refresh (which is very
unlikely, http responses are much cleaner) then I would be very interested in
knowing if the document was valid or not.

There are also those circumstances where a meta refresh is used, but not to
redirect a moved page. For example, a slide show with a refresh endlessly
cycling to the next page in looped sequence every 20 seconds.
Comment 4 Bj 2004-08-06 02:58:19 UTC
Note that I was talking about the documents linked from that document and that 
I was not suggesting to do that by default, just that the Validator should be 
able to do that if I want it to do that.
Comment 5 Terje Bless 2004-11-28 16:18:41 UTC
Yeah, probably not a bad idea to implement at some point.

Leaving Severity=Enhancement and reassigning default component owner
(resetting Status to NEW).