Howdy!

One person raised the issue. It Does Not Follow that no one else cares about the matter. Perhaps they don't have anything to add, so they simply say nothing. Just to be clear, I find the complaint to have merit (the one about tag misuse). Clearly, from this thread, I'm not alone. That's rather more than "one person"; you don't get a free pass to dismiss the concern that way.

The bottom line is that you *did* use spoiler tags for other than their intended purpose. That intent can be seen as patronizing -- "protecting" us from something "inconvenient".

...so, I decide to not remain silent, as that would encourage you to presume my consent in matters where you would be completely mistaken.

yours,
Michael Spikey Mace of Quiet Reason

In reply to Re^5: spoiler tag "abuse" by herveus
in thread spoiler tag "abuse" by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.