829 2004-07-24 13:29:28 +0000 Follow <meta http-equiv="refresh" ... 2007-03-29 18:48:23 +0000 1 1 1 Unclassified Validator check 0.7.0 Other other NEW P2 enhancement --- 1 bjoern link www-validator-cvs oldest_to_newest 2095 0 bjoern 2004-07-24 13:29:28 +0000 The Validator should be able to follow <meta http-equiv="refresh" ...> to ease batch validation for many pages with unknown content. 2113 1 link 2004-08-05 08:14:38 +0000 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? 2115 2 bjoern 2004-08-05 17:50:37 +0000 E.g. for http://www.w3.org/Consortium/Member/List 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? 2117 3 david 2004-08-06 02:41:05 +0000 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. 2118 4 bjoern 2004-08-06 02:58:19 +0000 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. 2660 5 link 2004-11-28 16:18:41 +0000 Yeah, probably not a bad idea to implement at some point. Leaving Severity=Enhancement and reassigning default component owner (resetting Status to NEW).