comment on

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"

In reply to Re: Re: •Re: Tweaks Made to FullPage Chat by arturo
in thread Tweaks Made to FullPage Chat by footpad

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks