Moodle 3.5.6+ (Build: 20190614)
Theme Classic theme_classic_moodle35_2018082000 and Boost 2018051400 (default in the core)
As the various screen-shots demonstrate, FontAwesome renders in content but not in headings. Is it possible to get them also in the headings?
My apologies! I have posted a comment in under FontAwesome filter.
In reply to Visvanath Ratnaweera
Re: FortAwesome does not render in headings
In reply to Adrian Perez Rodriguez
Re: FortAwesome does not render in headings
In reply to Visvanath Ratnaweera
Re: FortAwesome does not render in headings
In reply to Adrian Perez Rodriguez
Re: FortAwesome does not render in headings
In reply to Visvanath Ratnaweera
Re: FortAwesome does not render in headings
Found another missing piece: Site administration > Appearance > HTML settings > Remove HTML tags from all activity names (formatstringstriptag) was set, which was the default. Unticked and now FA icons also appear in headings.
It is still not satisfactory. Somehow the icon in the heading is "backspaced". See pic.
It is still not satisfactory. Somehow the icon in the heading is "backspaced". See pic.

In reply to Visvanath Ratnaweera
Re: FortAwesome does not render in headings
Hello Visvanath
Thanks for your findings, you're absolutely right. I updated the documentation in the Moodle plugins repository.
The other problem is as I see, only when you are _not_ in edit mode. The difference is, that in edit mode the activityinstance-inner is wrapped in an
Thanks for your findings, you're absolutely right. I updated the documentation in the Moodle plugins repository.
The other problem is as I see, only when you are _not_ in edit mode. The difference is, that in edit mode the activityinstance-inner is wrapped in an
<span>
element. Without an own hack (probably CSS) or changes in Moodle core we can not offer you another solution.Edit.
As I see it's because of these lines in Moodle core:
.section .activity .contentwithoutlink>a, .section .activity .activityinstance>a {
display: block;
text-indent: -31px;
padding-left: 31px;
}
Unset both values would solve the problem. But I don't know why these CSS values are applied. It seems to me that it doesn't make a difference.
HTH,
Adrian
HTH,
Adrian
In reply to Adrian Perez Rodriguez