Add font awesome custom renderer
What does this MR do?
It ensures that inline html font awesome within a markdown file isn't editable in WYSIWYG mode. This was left has HTML vs. plain text intentionally but we can later go that route if desired. From a UX lens we could:
- convert to plain text instead
- load the used font awesome icons and render them (and/or make a dedicated editor for users, YAGNI for now)
Screenshots
Before | After |
---|---|
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #221083 (closed)
Edited by Derek Knox