Re: Parsing of Refresh header/meta http-equiv in mobileOK

On Mon, 03 Mar 2008 17:38:17 +0100, Dominique Hazael-Massieux <dom@w3.org>  
wrote:
> I think we need to spell out what we assume is going to be parsed; a
> typical refresh header looks like:
> <META HTTP-EQUIV=Refresh CONTENT="10; URL=http://example.org/" />
> but mobileOK doesn't say what to do when there is no number, when there
> is only a URL, when there is space in this, etc.

Note that HTML 5 covers this in detail:

   http://www.whatwg.org/specs/web-apps/current-work/#refresh


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>