Fix: mobile TMA operator layout, Back and Cancel navigation - #20
Draft
EpicStarAi wants to merge 1 commit into
Draft
Fix: mobile TMA operator layout, Back and Cancel navigation#20EpicStarAi wants to merge 1 commit into
EpicStarAi wants to merge 1 commit into
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
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.
Problem
On Telegram mobile, the
/tma/profileoperator bottom sheet had overlapping header/context/history content. The decorative drag handle occupied an unintended CSS Grid row, so the panel rendered five content rows against a four-row grid. The operator also lacked a distinct internal Back action and consistent Cancel wording.Fix
header / context / history / footerBackButton:58dvhwith minimum and safe viewport constraintshistoryscrolling withmin-h-0,overflow-y-auto, andoverscroll-containDeny / Allowlabels withОтмена / РазрешитьQA
100dvhcancelledUI andTELEGRAM_MUTATION=falseSafety
UI/layout-only change. No Telegram send, executor, or approval bypass is introduced.