Change disabled retweet icon #14373
Merged
Change disabled retweet icon #14373
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ClearlyClaire
changed the title
ClearlyClaire
force-pushed
the
fixes/retweet-slash
branch
from
3fb73f7 to
a6a8d30
Compare
Gargron
approved these changes
Jul 22, 2020
shouo1987
pushed a commit
to CrossGate-Pawoo/mastodon
that referenced
this pull request
Dec 7, 2022
* Change disabled retweet icon * Hide fontawesome version of boost icon in both reduce-motion and no-reduce-motion
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The design is inspired by that of the
bell-slashfontawesome icon.Note: to make this work properly with the “reduce motion in animations” (which had no visible difference between disabled and enabled boost icon, btw; as well as slight alignment issues with both versions of the button), I had to disable the subtle color transition when boosting/unboosting. I guess this could be avoided if significantly refactoring this to use
svg:use.Before
After