Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ui): Specify a non-versioned FontAwesome #166

Merged
merged 1 commit into from
Apr 8, 2024

Conversation

NickHastings
Copy link
Contributor

@NickHastings NickHastings commented Mar 8, 2024

The current css specifies "FontAwesome 5 Free Solid", for .drawing and .text-button. This results in the button icons/fonts not rendering correctly on systems that do not have that exact version of FontAwesome. This change allows the icons/fonts to be rendered correctly on these systems.

This should resolve issues like #91 without users having to modify their local gtk css configurations.

BTW, I'm really liking swappy: IMO it has just the right balance of ease of use vs features. Thanks for the great software.

@NickHastings NickHastings changed the title fix(ui): Don't specify FontAwesome version fix(ui): Specify a non-versioned FontAwesome Mar 11, 2024
@jtheoof jtheoof self-assigned this Apr 7, 2024
@jtheoof
Copy link
Owner

jtheoof commented Apr 7, 2024

Thanks @NickHastings the commit does not respect the convention. fix(ui): specify a non-versioned FontAwesome (lower case subject).

@NickHastings NickHastings force-pushed the fix-fontawesome branch 2 times, most recently from 29fd018 to b260e94 Compare April 8, 2024 07:00
The current css specifies "FontAwesome 5 Free Solid", for .drawing and
.text-button. This results in the button icons/fonts not rendering
correctly on systems that do not have that exact version of
FontAwesome. This change adds the more generic "FontAwesome" as an
option allowing the icons/fonts to be rendered correctly on these
systems.
@NickHastings
Copy link
Contributor Author

NickHastings commented Apr 8, 2024

I removed all capitalization from the first line in the commit log. Is that what is required?
And also rebased since there was a commit.

@jtheoof jtheoof merged commit 3941fec into jtheoof:master Apr 8, 2024
3 checks passed
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