In features_admin_form() some markup is actually injected into the description to add information on conflicts, dependencies and requirements, however the description is later being outputted using check_plain() which escapes the markup and just looks weird. Simple patch on its way.

CommentFileSizeAuthor
#2 features-escape-markup-1885482-2.patch1.86 KBalexweber
#1 features-escape-markup-1885482-1.patch1004 bytesalexweber
Screen Shot 2013-01-10 at 5.08.42 PM.png109.92 KBalexweber
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

alexweber’s picture

alexweber CreditAttribution: alexweber commented
Status: Active » Needs review
FileSize
features-escape-markup-1885482-1.patch1004 bytes

Since the information comes from a module's .info file its safe to avoid running check_plain() on it IMO.

alexweber’s picture

alexweber CreditAttribution: alexweber commented
FileSize
features-escape-markup-1885482-2.patch1.86 KB

After looking at the 2.x branch I realised I had missed two more unneeded check_plains() in the string substitutions from l()

hefox’s picture

hefox CreditAttribution: hefox commented
Issue summary: View changes

Is this 1.x only?