<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Excellent work Jonathan.<div><br></div><div>Stephen<br><br><div>> Date: Wed, 5 Oct 2011 15:49:28 -0400<br>> From: jrogers@socialserve.com<br>> To: twill@lists.idyll.org<br>> Subject: [twill] meta http-equiv refresh content syntax<br>> <br>> I have removed Twill's ancient copy of mechanize and made it work with a<br>> regular, current distribution. One test currently fails because of a<br>> disagreement about how to interpret the content attribute of a meta<br>> http-equiv="refresh" element:<br>> <br>> <meta http-equiv="refresh" content="0;'URL=/login'"><br>> <br>> The test script (test-equiv-refresh.twill) expects the above to cause a<br>> load of "/login". It seems that's what the ancient internal version of<br>> mechanize did, but a current version tries to load "URL=/login" which<br>> results in a 404. This is exactly the same behavior I get in Firefox,<br>> Chromium, and Epiphany.<br>> <br>> If the test is correct and typical browsers are not, what's the real<br>> authority? I'm having trouble even finding a formal definition of the<br>> syntax the content attribute is supposed to have.<br>> <br>> -- <br>> Jonathan Ross Rogers<br>> <br>> _______________________________________________<br>> twill mailing list<br>> twill@lists.idyll.org<br>> http://lists.idyll.org/listinfo/twill<br></div></div> </div></body>
</html>