Fixed: GitHub Issue #29530 - Missing Expandable Quote Button in Caption Field #30179
+1
−0
Conversation
This file contains hidden or 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
… Button in Caption Field
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem: When composing a message with media/files, the button to convert quotes to "expandable quotes" was missing from the caption field, even though it works in the regular message input.
Root Cause: The caption field used a style (boxTextStyle via defaultInputField) that had an empty blockquote configuration with no expand/collapse icons. The main message input uses historyTextStyle which has properly configured blockquote icons.
Fix: Added style: historyTextStyle; to defaultComposeFilesField in Telegram/SourceFiles/chat_helpers/chat_helpers.style:1436.
This one-line change affects all caption fields that use this style:
fix #29530