11597 2010-12-23 09:15:22 +0000 mismatch between parsing rule and valid syntax for meta refresh URL 2011-08-04 05:02:57 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows NT RESOLVED FIXED http://bugzilla.validator.nu/show_bug.cgi?id=762 P2 normal --- 1 julian.reschke ian ian mike public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 43522 0 julian.reschke 2010-12-23 09:15:22 +0000 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". 43843 1 ian 2011-01-06 05:36:32 +0000 I'll change it to say "...a valid URL that does not contain any literal U+0027 APOSTROPHE (') or U+0022 QUOTATION MARK (") characters". Though if those are really allowed, I'm sure there's got to be other places where I screwed that up. Adam, your spec only defines parsing, right? Not allowed syntax? 43844 2 ian 2011-01-06 05:46:06 +0000 zcorpan suggests s/does not contain any/does not start with a/, which seems reasonable. 43845 3 w3c 2011-01-06 05:48:23 +0000 > Though if those are really allowed, I'm sure there's got to be other places > where I screwed that up. Adam, your spec only defines parsing, right? Not > allowed syntax? That's correct. 45203 4 ian 2011-02-07 22:47:24 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: The conformance criteria for authors should not be inconsistent with the parsing rules for implementors. 45204 5 contributor 2011-02-07 22:47:48 +0000 Checked in as WHATWG revision r5840. Check-in comment: Disallow URLs that would conflict with the way meta refreshes are parsed. http://html5.org/tools/web-apps-tracker?from=5839&to=5840 52598 6 mike 2011-08-04 05:02:57 +0000 mass-moved component to LC1