You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 25cd9f4
Browse filesBrowse the repository at this point in the historyBrowse files
Chat: an unsupported message's plate keeps what a message has — its side, a post's buttons, selection, reading
The plate came in drawn on the service path, which returns before everything the chat does for a message, so
it lost that piece by piece: an outgoing one could hold the unread delimiter, a report's choice and a swipe to
reply passed it by, a channel post lost its share and comments buttons, its views and its reading, a forward on
its way could be selected, a protected channel's post kept a share button, an ad anchored after it was dropped.
- It is drawn on the regular path now, as the content of a bubble with no background of its own, the way a
sticker stands (`just-media`), so all of that comes with it by construction. What it shows stays Android's
plate alone: no time (`noMessageInfo`, as a call has), no name, no forward header, no quote; a saved copy
keeps its button to where it was saved from.
- A post's comments stand beside the plate, as beside a sticker; a broadcast post with no time to be read by
is watched itself.
- A rich message whose media this client cannot show keeps its rich content, as before.
- The plate gives way to a column narrower than it instead of running past its edge.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
"Message.Unsupported.Desktop" = "__This message is currently not supported on Telegram Web. Try [getdesktop.telegram.org](https://getdesktop.telegram.org/)__";
479
479
"Message.Unsupported.Mobile" = "__This message is currently not supported on Telegram Web. Try [telegram.org/dl](https://telegram.org/dl/)__";
0 commit comments