Make WordPress Core

Opened 10 years ago

Closed 7 years ago

#7869 closed enhancement (wontfix)

Colorizing comments should be enabled

Reported by: huji Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Comments Keywords: close
Focuses: Cc:


At the moment, only BBcode (or a limited version of it?) is allowed in comments. I suggest we upgrade this, so people (or at least admins) could use color in their comments.

One usage of this is when the author of the blog decides to reply to comments inside them, not as separate comments: he can write in a different color.

Change History (9)

#1 @DD32
10 years ago

If you're an admin, You can use any HTML in comments AFAIK, That includes using font tags with color attribute, or using the style attribute.

I wasnt even aware that BBCode was used by WordPress?(Actually, Doesnt appear so)

The HTML tags which general commenters can use is highly restricted in order to prevent a malicious comment running JS or inserting malicious content, JS can be executed via the style attribute under IE AFAIK, as well as a few other attributes which should be generally 'safe'..except when using certain browsers.

#2 @DD32
10 years ago

Okay, Scratch that.. <font color="red">Test</font> is indeed striped out.. Though i'm pretty sure that worked at one stage, <p style="color:red">Red</p> however does work.

I thought the idea of _wp_unfiltered_html_comment was to allow for admins to enter the HTML they want without WP stripping it out.

#3 @huji
10 years ago

Another approach is to reduce the restrictions of html code in comments, if an admin is posting the comment. Generally, I see no harm in letting (all of) users to post <span> tags with style attributes.

#4 @mrmist
10 years ago

<font> tags are deprecated anyway, though the point about "unfiltered" is valid nevertheless.

I'm not really sure how this enhancement is meant to be implemented, seeing as you can achieve it already through code and/or themes (as an admin) and opening up colours to non-admins would potentially give you a big, unreadable, mess.

#5 @ryan
9 years ago

  • Milestone changed from 2.8 to Future Release

#6 @Denis-de-Bernardy
9 years ago

  • Component changed from General to Comments
  • Owner anonymous deleted

#7 @Denis-de-Bernardy
9 years ago

  • Keywords needs-patch added

#8 @solarissmoke
7 years ago

  • Keywords close added; needs-patch removed

This looks like plugin material to me..

#9 @scribu
7 years ago

  • Milestone Future Release deleted
  • Resolution set to wontfix
  • Status changed from new to closed


Note: See TracTickets for help on using tickets.