Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Like at least several other monks (that I know of), I have some "template" information in my signature. With that patch, I'd end up typing my entire node content within the "sig" unless I remember (every single time I post) to move things around.

But I think that problem can be addressed by a minor improvement to the patch: Only add the tags if they aren't already present in the signature. Then I can update my signature one time to incorporate the new tags (which I can cut-n-paste from a quick "preview") and never have to move parts after that.

Other than that, I worry that perhaps we need to think a little more about the tag. I'm anything but a CSS expert, so I'll ask some dumb questions. I guess div is a better choice than span since a signature really shouldn't be an in-line entity. Someone already gave an example of apply custom CSS to all sigs. Is that type of wildcarding common in browsers supporting CSS? Or should we have both a per-user tag and a all-sigs tag? Perhaps something like <div class="pmsig" id="pmsig-22609">?

I'd rather get that right the first time than have to worry about backward compat when we realize we didn't as good as we could.

Thanks for the idea, adrianh, for the patch, chromatic, and for the future feedback, y'all.

                - tye

In reply to Re^3: Add CSS class for signatures? (repatch) by tye
in thread Add CSS class for signatures? by adrianh

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



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (1)
As of 2023-06-08 00:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How often do you go to conferences?






    Results (29 votes). Check out past polls.

    Notices?