- From: <bugzilla@jessica.w3.org>
- Date: Thu, 23 Dec 2010 09:15:23 +0000
- To: public-html@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11597 Summary: mismatch between parsing rule and valid syntax for meta refresh URL Product: HTML WG Version: unspecified Platform: PC URL: http://bugzilla.validator.nu/show_bug.cgi?id=762 OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: julian.reschke@gmx.de QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-wg-issue-tracking@w3.org, public-html@w3.org See http://dev.w3.org/html5/spec/Overview.html#attr-meta-http-equiv-refresh "For meta elements with an http-equiv attribute in the Refresh state, the content attribute must have a value consisting either of: * just a valid non-negative integer, or * a valid non-negative integer, followed by a U+003B SEMICOLON character (;), followed by one or more space characters, followed by a substring that is an ASCII case-insensitive match for the string "URL", followed by a U+003D EQUALS SIGN character (=), followed by a valid URL." This makes the following string conforming <meta http-equiv="Refresh" content="20; URL='foo'bar'"> as 'foo'bar is a valid URI reference according to RFC 3986. However, the parsing instructions special case leading ' and " characters, and will truncate at the 2nd occurence, so the value is actually handled as foo The conformance criteria apparently need to take surrounding quoted into account, may be by defining "valid optionally quoted URL". -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 23 December 2010 09:15:25 UTC