Problem/Motivation
When entering a field description that includes a html entity as text &, the text is converted to a html entity on the form &.
For example:
Use ­ to control where the hyphen is placed in the browser when the word is displayed over two lines.
Results in:
Use - to control where the hyphen is placed in the browser when the word is displayed over two lines.
Proposed resolution
Display the same on the form as is entered in the field settings form.
Remaining tasks
- Write a patch
- Review
- Commit
User interface changes
When a field description includes a html entity as text, the html entity is rendered as the same text on the form.
API changes
None.
Data model changes
None.
Comments
Comment #9
finneThe field description is rendered as HTML. So if you want to print literal HTML (entities or tags) you should double print/escape them:
&works.Differentiating between html that should be interpreted, stripped or printed literally is too complicated here I think.
What could be improved is the help description underneath the "field description" field. This should point out that all HTML will be either interpreted or stripped. I propose we change this issue from bug to task to do this.
A further, more complicated enhancement would be to allow a text format to be defined for this field so you can use CK editor on it.
Comment #12
enaznin commentedAdded a patch to update the help text as per the suggestion in #9