• Resolved Jer Clarke

    (@jeremyclarke)


    Maybe it’s too late for this idea because people already added span.shortcode in their CSS (rather than just .shortcode which seems more likely), but it seems like your plugin would be an ideal use of the <code> HTML tag. It’s display: inline; like span, but would mean that all themes with CSS for <code> magically have nice monospace fonts etc for .shortcode output.

    It was easy enough for me to edit my CSS and add .shortcode wherever I saw code, but for people using default or off-the-shelf themes it would be a huge pain to have to copy all the code CSS into their child theme/custom-css just to get the same effect (and most won’t ever do it anyway). If you used the <code> tag it would be automatic and they’d never even need to think about it.

    Thanks again for the plugin!

    https://www.ads-software.com/plugins/shortcode-shortcode/

Viewing 1 replies (of 1 total)
  • Plugin Author cubecolour

    (@numeeja)

    Thank you for the suggestion, I can see how it would be an improvement. The simple answer is that I didn’t think of doing this when the plugin was made.

    It is a very niche plugin with only 40 active installs so updating it isn’t a major priority, but I don’t think this change should cause too many problems with backward compatibility so once I have had a chance to check this on my test sites I might update the plugin.

Viewing 1 replies (of 1 total)
  • The topic ‘Why not use code.shortcode rather than span.shortcode’ is closed to new replies.