comment on

The explanatory text was removed because two of us felt that the manner in which it was given to the user was quite annoying (pre-pasted into the message composition window such that every user with a signature would have to delete the lengthy text every time they replied until they took the time to update their signature).

Oh dear. It seems my comment was interpreted as being a negative one. Not my intention.

But it is true that I do disagree with the decision. I see the message my original patch would have provided as being signifigantly less annoying than simply having the new tags added without any explanation.

But as I feel a touch of responsibility for the present state of affairs Ill look into a patch along the lines you've suggested. Perhaps when the form is constructed a note could be added underneath if the tags have been automatically added pointing to the documentation of the feature?

---
demerphq

_{First they ignore you, then they laugh at you, then they fight you, then you win.

-- Gandhi}

In reply to Re: Re^5: [CSS] Let's discuss Podmaster's Signature (help text) by demerphq
in thread Let's discuss Podmaster's Signature by princepawn

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.


The stupid question is the question not asked
	PerlMonks