But people use those undocumented quirks in browser
implementation. I don't think we could ever banish
reliance on such non-standard features, so maybe the best
way to deal with them would be to incorporate them to the
RFC in substitution of the original spec (I'm not talking
specifically about this one quirk, which you say is unsafe;
BTW, would you dwell into why it is so?).
PerlMonks itself, doesn't it rely on Netscape's redirect
after POST behavior?
Also, consider that Perl is a good example of the
implementation being also the standard, a system
that has worked pretty well, IMHO.
-
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.
|
