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.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||