This is the refresh meta tag as it is now:
<meta http-equiv="refresh" content="12; url='/index.pl?displaytype=ra
+w&node_id=3200'" />
According to several tutorials I found, one shouldn't put those single quotes around the URL, for example Webmonkey and indiana.edu.
So this tag should really look like:
<meta http-equiv="refresh" content="12; url=/index.pl?displaytype=raw
+&node_id=3200" />
At least merlyn's browser falls over the presence of that opening single quote. | [reply]
[d/l]
[select] |
<meta http-equiv="refresh" content="12; url=/index.pl?displaytype=raw
+&node_id=3200" />
You forgot the HTML escaping step. Just like most of Everything2 does, last time I looked. And it's all broken.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply. | [reply]
[d/l]
[select] |
Discussion of this issue went on for a while, so I'll just sum it up here:
Nobody was able to find anything constituting anything like a W3C standard governing the content of content attributes of meta refresh tags. bart is correct in pointing out, (AFAIK) that no browser appears to fail if the single quotes around the URL "sub-attribute" are omitted, so if the darn things are going to be used and not proper HTTP headers, well, then it's best to omit the quotes (although I found examples containing quotes on a site owned by the same miscreants that appear to have invented this mess.
W/ most browsers, the "sub-attribute" is only needed if the refresh tag is one of those cheesy redirects (my technical term of choice). Refreshing the same page needs only a time.
For those of you who are interested, this was the closest thing I could find to a "reference" on the subject. Yes, not only did they invent <blink>, this, too is their fault =)
If not P, what? Q maybe?
"Sidney Morgenbesser"
| [reply]
[d/l] |
| [reply] |
| [reply] |
