Hi, in the backend the Profiles icon is missing, looking at the source code it seems to me that there is a conflict between icoMoon and Fontawesome that I use and load in my site?

<span class="fa fa-users icon-users" aria-hidden="true" role="presentation"></span>

infact if I delete "fa fa-users" it works using icomoon. thanks Giuse

Ok, can we abandon incombono and use only fontawesome since joomla v4 did that at least for the front-end?
Cheers

Hi, the site is loading fontawesome in backend since content (articles) are using those icons

Sorry, I am not getting the point: in J3 with standard Joomla backend template "isis", JCE is adding the Users icon as

class="fa fa-users icon-users"

that is the typical syntax for fontawesome but the icons are taken from icomoon since isis css sets font-family with

[class^="icon-"]:before,
[class*=" icon-"]:before {
	font-family: 'IcoMoon';
	font-style: normal;
	speak: none;
}

this is not an issue of JCE? thanks

Sorry, I can't agree: also in J4 JCE uses icomoon for control panel icons and not fontawesome, so why invoking fontawesome? At least it is unuseful to trigger css that is not relevant to what needs to be displayed and causes possible conflict, exactly like in this case. Look at the file browser icon (in the control panel): it is now

<span class="fa fa-picture icon-picture" aria-hidden="true" role="presentation"></span>

[list] [*]try to delete "fa fa-picture" => nothing happens since this fontawesome class it is redundant; [*]try to delete "icon-picture" => icon disappears, because JCE is using only this icomoon syntax. [/list]. So my question is: why adding unuseful classes that can lead to conflict, by the way with fontawesome that is so widely used? I don't want to be pedantic, so I will not insist any more but I seem the way icons in the control panels are invoked is not "clean". thanks for your patience