Skip to content

FontAwesome 5 compatibility#665

Closed
Ionaru wants to merge 2 commits intosparksuite:masterfrom
Ionaru:patch-1
Closed

FontAwesome 5 compatibility#665
Ionaru wants to merge 2 commits intosparksuite:masterfrom
Ionaru:patch-1

Conversation

@Ionaru
Copy link
Copy Markdown

@Ionaru Ionaru commented Dec 2, 2017

  • Icons from FA5 should now work, but you have to use the fa-v4-shims to get all the icons right.
  • FA4 icons still work like they used to.
  • Fixes FontAwesome 5 compatibility #664

* Icons from FA5 should now work, but you have to use the fa-v4-shims to get all the icons right.
* FA4 icons still work like they used to.
@Ionaru
Copy link
Copy Markdown
Author

Ionaru commented Dec 2, 2017

Not sure what's up with the tests, afaik I didn't change anything in that long scary isMobile function. Can @WesCossick look into this?

* Removed redundant escapes from isMobile regex and some others.
* Added fa-heading class to heading icon so it works on FA5.
* Changed fa-picture-o to fa-image so it works on FA5.
* Added noDisable flag for icons that is then handled in the createIcon function.
* Changed 'http://' default for links to 'https://'.
* Added noDisable to guide icon.
* Removed opacity change on toolbar hover (was 0.6).
* Removed opacity default (was 0.8).
* Removed default icon color (was #2c3e50).
* Added opacity change to disabled buttons, they get opacity of 0.6 when disabled.
* Added Node 8 and Node 9 support.
* Removed Node 0.12 and Node 5 support.
@Ionaru
Copy link
Copy Markdown
Author

Ionaru commented Dec 4, 2017

Closing this because I made a new PR on the develop branch. ( #666 )

@Ionaru Ionaru closed this Dec 4, 2017
@Ionaru Ionaru deleted the patch-1 branch December 5, 2017 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant