chromium/src/third_party/blink/web_tests/http/tests/misc/meta-http-equiv-and-name.html - manifest_repos/chromium_src - Git at Google

 <!DOCTYPE html>
 <html>
 <head>
 <script>
 if (window.testRunner) {
     testRunner.dumpAsText();
     testRunner.waitUntilDone();
 }
 </script>
 <meta http-equiv="refresh" name="unknown" content="0; url=resources/success-notify-done.html">
 </head>
 <body>
 <a href="http://crbug.com/332090">http://crbug.com/332090</a><br/>
 The handling of an &lt;meta&gt; element having both a 'name' and
 'http-equiv' attribute should be disambiguated gracefully. Even if
 the specification requires that at most one should be used.
 </body>
 </html>
	<!DOCTYPE html>
	<html>
	<head>
	<script>
	if (window.testRunner) {
	testRunner.dumpAsText();
	testRunner.waitUntilDone();
	}
	</script>
	<meta http-equiv="refresh" name="unknown" content="0; url=resources/success-notify-done.html">
	</head>
	<body>
	<a href="http://crbug.com/332090">http://crbug.com/332090</a><br/>
	The handling of an <meta> element having both a 'name' and
	'http-equiv' attribute should be disambiguated gracefully. Even if
	the specification requires that at most one should be used.
	</body>
	</html>