W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > January to March 2008

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

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 03 Mar 2008 17:48:32 +0100
To: "Dominique Hazael-Massieux" <dom@w3.org>, "Sean Owen" <srowen@google.com>, "Jo Rabin" <jrabin@mtld.mobi>
Cc: public-bpwg-comments <public-bpwg-comments@w3.org>
Message-ID: <op.t7f8y6ed64w2qv@annevk-t60.oslo.opera.com>

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/>
Received on Monday, 3 March 2008 16:49:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 June 2012 12:13:31 GMT