The user client should display the messages.botResults.results obtained during querying in a list, making sure to handle eventual bot timeouts in the form of a BOT_RESPONSE_TIMEOUT RPC error, by simply not displaying anything.
If either the messages.botResults.switch_pm or messages.botResults.switch_webview flags are populated, a button should be displayed on top of the result list, that when clicked, instead of sending an inline result to the chat, switches the user to a private chat with the bot (switch_pm) or to a bot web app (switch_webview),.
If either the messages.botResults.switch_pm or messages.botResults.switch_webview flags are populated, a button should be displayed on top of the result list, that when clicked, instead of sending an inline result to the chat, switches the user to a private chat with the bot (switch_pm) or to a bot web app (switch_webview).
If the user instead chooses a specific BotInlineResult from the normal results list, the messages.sendInlineBotResult method should be invoked, passing:
query_id from messages.botResultswhitelisted_domains
A list of Telegram domains that can always be opened without additional user confirmation, when clicking on in-app links where the URL is not fully displayed (i.e. messageEntityTextUrl entities). (array of strings)
Note that when opening named bot web app links for the first time, confirmation should still be requested from the user, even if the domain of the containing deep link is whitelisted (i.e. t.me/<bot_username>/<short_name>?startapp=<start_parameter>, where t.me is whitelisted).
Confirmation should always be asked, even if we already opened the named bot web app before, if the link is not visible (i.e. messageEntityTextUrl text links, inline buttons etc.).
round_video_encodingContains a set of recommended codec parameters for round videos. (object, as described in the example)
chat_read_mark_size_thresholdWallpapers can also be installed in a specific chat, by using messages.setChatWallPaper: this will emit a messageActionSetChatWallPaper service message, displaying the wallpaper in the UI along with an invitation for the other user to apply the same wallpaper.
-If the other user decides to apply the same wallpaper to the chat, messages.setChatWallPaper should be invoked passing the wallpaper settings received in the messageActionSetChatWallPaper service message, along with the id of the messageActionSetChatWallPaper service message, without the wallpaper: this way, the action will emit a different messageActionSetSameChatWallPaper, which should be displayed in the UI as a simple acknowledgment service message, without the full wallpaper and without an invitation for the other user to apply it (since both participants already just did that).
If the other user decides to apply the same wallpaper to the chat, messages.setChatWallPaper should be invoked passing the wallpaper settings received in the messageActionSetChatWallPaper service message (or some different settings, if the user customized them before applying the wallpaper), along with the id of the messageActionSetChatWallPaper service message, without the wallpaper: this way, the action will emit a different messageActionSetSameChatWallPaper, which should be displayed in the UI as a simple acknowledgment service message, without the full wallpaper and without an invitation for the other user to apply it (since both participants already just did that).
Note that in order to pass image or pattern wallpapers to messages.setChatWallPaper, the for_chat flag must be set when uploading them with account.uploadWallPaper.
Also note that unlike account.installWallPaper or account.saveWallPaper, messages.setChatWallPaper accepts fill wallpapers as well.
diff --git a/data/web/corefork.telegram.org/constructor/messageEntityTextUrl.html b/data/web/corefork.telegram.org/constructor/messageEntityTextUrl.html index 49183ae294..c7e0739cdb 100644 --- a/data/web/corefork.telegram.org/constructor/messageEntityTextUrl.html +++ b/data/web/corefork.telegram.org/constructor/messageEntityTextUrl.html @@ -42,7 +42,7 @@Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
+Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
Note that an additional confirmation popup with the full URL must be displayed to the user before opening this link, unless the domain is one of the whitelisted domains specified in the whitelisted_domains client configuration parameter ».
How to create styled text with message entities
Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
+The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
How to create styled text with message entities
Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
+Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
+Note that an additional confirmation popup with the full URL must be displayed to the user before opening this link, unless the domain is one of the whitelisted domains specified in the whitelisted_domains client configuration parameter ».
whitelisted_domains client configuration parameter ».