fix: "Show in Chat" in gallery not working #4629
Merged
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
WofWca
force-pushed
the
wofwca/fix-jumpToMessage-from-gallery
branch
from
34109bc to
a8faa52
Compare
WofWca
force-pushed
the
wofwca/fix-jumpToMessage-from-gallery
branch
from
a8faa52 to
b336bc9
Compare
WofWca
force-pushed
the
wofwca/fix-jumpToMessage-from-gallery
branch
from
a8d5748 to
5730919
Compare
WofWca
force-pushed
the
wofwca/fix-jumpToMessage-from-gallery
branch
from
5730919 to
1f536ff
Compare
WofWca
force-pushed
the
wofwca/fix-jumpToMessage-from-gallery
branch
from
1f536ff to
f4806bc
Compare
i.e. ensure that `__internal_check_jump_to_message` was set by this component instance prior to resetting it. This doesn't appear to fix any current bugs, but hopefully will save us later.
WofWca
force-pushed
the
wofwca/fix-jumpToMessage-from-gallery
branch
from
f4806bc to
d8ffa75
Compare
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 bug was likely introduced in
#4554
(da4b916).
FYI the bug has only been released with 1.53.0.