I have tested this item ✅ successfully on 1b4894d

It does no need, there already fontawesome asset, in media/vendor/joomla.asset.json
And a fix for font-face files in #31364

hm I have missed "icomoon" changes.
if someone need "icomoon" then ignore my previous comment ?

I would expect the fontawesome css to be the same just in a different location etc. But

It does no need, there already fontawesome asset, in media/vendor/joomla.asset.json
And a fix for font-face files in #31364

I didn't see your PR before I did mine... And I was not aware of fontawesome as an asset in the media/vendor/joomla.asset.json file :-(
As I understand the icomoon file contains a mapping old icomoon => new fontawesome. I think it is important to include.

@brianteeman the code in your screenshot is included in Autum but not in Cassiopeia
Because Autum loads also an own fontawesome file

I think here some confusion,
Cassiopeia already have templates/cassiopeia/scss/vendor/fontawesome-free/fontawesome.scss that holds fontawesome and icomoon.

And media/vendor/joomla.asset.json already holds fontawesome Asset.

The final file templates/cassiopeia/css/vendor/fontawesome-free/fontawesome.css overrides file from media/vendor/fontawesome-free/fontawesome.css, and so fontawesome Asset uses fontawesome.css provided by Cassiopeia.

All is working good already, you do not need to fix anything ?

I'm developing a J4 template without Bootstrap and with a parameter to switch fontawesome on / off. It works good. But if I want to use frontend editing, I need fontawesome (or I have to re-define the icons). I don't want to deliver an own version of fontawesome with the template (and Cassiopiea shouldn't do either), I want to load what Joomla already has in core. And I want to be able to load fontawesome only in component.php for the frontend editing. If the version of fontawesome in Joomla core doesn't include the font-face and the icons mapping, it will not work.

@Fedik The problem being solved is that a template might not use fontawesome but when you open an edit form on the front end then you will need to load fontawesome. So by making it available as an asset it can be added into the edit forms

When I write fontawesome I mean the fontawesome WITH iconmoon conversion file

So by making it available as an asset it can be added into the edit forms

As I already noted before: the fontawesome already provided by media/vendor/joomla.asset.json.
media/vendor/joomla.asset.json always loaded, and available for all extensions.

I'm developing a J4 template without Bootstrap and with a parameter to switch fontawesome on / off.

if you doing it in your personal template then all you need is something like:

if ($needToEnableFont) 
{
  $wa->useStyle('fontawesome');
}

If you want this in Cassiopiea, then you have to remove these dependencies from Cassiopiea joomla.asset.json:

And then use in PHP:

if ($needToEnableFont) 
{
  $wa->useStyle('fontawesome');
}

If the version of fontawesome in Joomla core doesn't include the font-face and the icons mapping, it will not work.

The fontawesome in Joomla core contains only original fontawesome style and icons, without mapping to Joomla icons.
These mapping done by the template itself (eg templates/cassiopeia/scss/vendor/fontawesome-free/fontawesome.scss).

If people want to have Joomla "icomoon" Independently from the template, then we probably need to re-compile fontawesome in media/vendor. But this is totally different topic.

hm, sorry, I think I am Turtle ?

I finally understood what you tries to do, it a bit in confusing way, but it is okay.

The PR is okay for its purpose.

Sorry again ?

Also, another comment here: ALL the fields should use SVG icons either as HTML or as css background so that the front end WILL BE font awesome free. Icon fonts are really deprecated and should be considered HARMFUL as their killing performance metrics but also have serious caveats for visually impaired people.

also have serious caveats for visually impaired people.

They are no better and no worse than svg. Its all down to how they are used.

They are no better and no worse than svg. Its all down to how they are used.

I suspect if everyone else dropped already font icons there are obvious drawbacks. Basically abusing Fonts for enhancing style was once an option (no SVG support in IE, etc) but those reasons have been eliminated since IE 11 which basically is like a decade ago. Time to move to something more in line with the actual web devs practices. My 2c anyways...

there are obvious drawbacks

I am only commenting on the repeated statement that they are not bad for accessibility or that SVG are good for accessibility

I am only commenting on the repeated statement that they are not bad for accessibility or that SVG are good for accessibility

SVG's (depending also on how you're using them) could be better one at least one case: if the network fails to deliver either the css or the actual font then the icons will not be displayed. Inlining (obviously cleverly, without blowing up the document size) eliminates this case. If you have the document you already have the icons ?. Anyways, there are more cases that fonts fall short for this particular usage but accessibility wise you can end up messing either. I never suggested that SVGs are by default accessible and icons are not but maybe the path to making something accessible could be easier with SVGs (purely because you will end up calling some PHP function that will do the right thing, instead of manually inserting HTML tags/attributes)

May I ask a question here?
I'm just a user, not a coder, but I don't know where else to ask.
I've made a test site with Beta8, and was happy to find FontAwesome installed locally.
However: I cannot use the brand icons (facebook, linkedin). Miscellaneous icons (bicycle, camera) display just fine.
Is there a reason for this?
Thanks.

@Mrs-Jaydot Questions on https://forum.joomla.org/

@sandramay0905 Thanks, I know, but no-one there has any idea. The only answer I got was "I don't think Joomla uses Font Awesome...".

@sandramay0905 Thanks, I know, but no-one there has any idea. The only answer I got was "I don't think Joomla uses Font Awesome...".

Are you using Cassiopeia or an own template?

@drmenzelit Cassiopeia.

There are multiple font files for fontawesome. Not all are free etc

@drmenzelit Cassiopeia.

<i class="fab fa-facebook"></i> should work (fab is for brands)

brands need a fab class, eg <i class="fab fa-facebook-f"></i>
fab === brands
far === regurlar
fas === solid

In short there are 3 fonts and if you load all of them your site will be blank for some time for first-time visitors...

@brianteeman I know, but FA4 is free for download, and it contains brand icons.
@drmenzelit Thank you!! Works! I didn't know about the faB.
@Fedik Thank you for responding and explaining, I didn't know it worked that way.
Many thanks to all of you.
I will now move back to forum.org, where I belong :).

Do we have to test this patch?

Do we have to test this patch?

@RickR2H In general yes, every PR needs 2 tests, but is currently has a conflict in file templates/cassiopeia/scss/vendor/fontawesome-free/fontawesome.scss, so better wait until that has been resolved.

@drmenzelit Is the PR still relevant? If yes, could you solve the conflict? Let me know if you need help with that. Thanks in advance.

The discussion was long, I got lost at some point... and it seems my approach is not clear for everyone, so I think it is up to @wilsonge to decide what to do with it

@ChristineWk Could you test again with the new packages for this PR? Thanks in advance.

I have tested this item ✅ successfully on 5b1a08d

works as described

I have tested this item ✅ successfully on 5b1a08d

Hv this (if it's OK):
/*!

• Font Awesome Free 5.15.3 by @FontAwesome - https://fontawesome.com
• License - https://fontawesome.com/license/free (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
  */

  ---

  _{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/32541.}

RTC

we created a auto .fa to .iconmoon conversion system long ago. idky it needs to be done in another way yet again.

we created a auto .fa to .iconmoon conversion system long ago. idky it needs to be done in another way yet again.

@N6REJ This PR here doesn't change anything on the mapping, it just moves scss to another place and makes it available as template-independent asset.

Its not being done in a different way its just putting the files in the correct place

Its not being done in a different way its just putting the files in the correct place

That's what I've said, too.

github cache sucks sometimes

Thanks guys, I was about to say, danggggg after all that work LOL

Thanks!