Skip to content

Conversation

@cienislaw
Copy link
Contributor

Updated Font Awesome to 4.7.0, but:

  • Commit doesn't include compiled CSS as last compiled commit was made 5 years ago. Since then browserslist include very different set of data, which has a great impact of result. It's not for me to decide to do this task.
  • There are some not needed files in Font Awesome folder;
  • font-awesome.css is compiled but not used as global.css uses FA with .icon prefix;

Updated Font Awesome to 4.7.0, but:

- Commit doesn't include compiled CSS as last compiled commit was made 5 years ago. Since then browserslist include very different set of data, which has a great impact of result. It's not for me to decide to do this task.
- There are some not needed files in Font Awesome folder;
- font-awesome.css is compiled but not used as global.css uses FA with .icon prefix;
@therampagerado
Copy link
Contributor

@cienislaw how hard would it be to update to the free versions 5 or even 6 with shims and local hosting?
I tried to make this change on local dev site but I was unable to figure out how the css is loaded so to include v4-shims.min.css.

@cienislaw
Copy link
Contributor Author

@therampagerado current v4 implementation in theme is backward compatible with font awesome v3 - it uses v3 'icon-' prefix instead of 'fa-' (introduced in v4), thats why including v4-shims from v6 does nothing.

to update to v6 and make it user-friendly for those who will buy PRO version, 'icon-' prefix needs to be dropped. I can prepare such branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants