Fix for bug with custom opacity #27
Open
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.
There is an issue with the current release which causes an issue with the text if the default
opacity
style prop is changed when calling the component. For instance, if someone were to call the<MarqueeText>
component as follows,then, a bug would cause the specified
opacity: 0.5
to take effect only once the text starts to move. Moreover, if the length of the string is short enough that there is no need for the marquee animation, then the whole text would stay at the default opacity.This pull request fixes the same.