Using "solid" versions of Font-Awesom font icons

[pauldugas]

I'm trying specifically to use Font Awesome's "expand-alt" icon.

iconCls: 'x-fa fa-expand-alt',

I know I need to add "fas" somewhere in there but all the combinations I've tried aren't working.

Any guidance?

[rrandymeyer]

Hi @pauldugas,

I don't think it's you. I just tried using the expand-alt in ExtJS 7.0.0.156 and it was not showing, expand and expand-arrows-alt both work fine.

-Rudy

[dawesi]

search the forums, you'll have to generate a whole new set of icons into a package then use that package.

just search for font-awesome-5 pro and you'll find them.... extjs only has free versions.

[pauldugas]

https://fontawesome.com/icons?d=gallery&q=expand&m=free

expand-alt appears to be part of the free set

[aicgroup-dev]

Hi Paul,

are you sure your application has set some kind of prefix (x-fa) ? try it without, then

fas fa-expand-alt

should work.

[pauldugas]

I agree that is "should" work Sadly, doesn't for me.

[pauldugas]

node_modules/@sencha/ext-font-awesome/sass/src/all.scss looks like it's defining x-fa along with x-fas, x-far and x-fab classes. I see -expand and -expand-arrows-alt in node_modules/@sencha/ext-font-awesome/sass/etc/_icons.scss but not -expand-alt. Looks to me like it was just missed.

[MadisonWisconsin]

I can't get your icon to work either.

Your icon's syntax is here:
https://fontawesome.com/icons/expand-alt?style=solid

But in my stand-alone test (not using ExtJS), it isn't showing up!

Here are the rules for prefixes.
https://fontawesome.com/how-to-use/o...cons/basic-use

Here's a little Fiddle showing what they look like in ExtJS.
https://fiddle.sencha.com/#view/editor&fiddle/32tk

[pauldugas]

Yes, "fa-expand-alt" is listed as one of the "fas" icons in your fiddle but the corresponding class isn't included in the ext-font-awesome package.

[MadisonWisconsin]

Yes, "fa-expand-alt" is listed as one of the "fas" icons in your fiddle but the corresponding class isn't included in the ext-font-awesome package.

I did a stand-alone test too -- not using ExtJS at all -- and it didn't show up there either. This looks like an issue with fontawesome itself.