diff --git a/data/web/corefork.telegram.org/api/bots/webapps.html b/data/web/corefork.telegram.org/api/bots/webapps.html index 85aed6d618..93f5657900 100644 --- a/data/web/corefork.telegram.org/api/bots/webapps.html +++ b/data/web/corefork.telegram.org/api/bots/webapps.html @@ -112,6 +112,7 @@ messages.requestSimpleWebView#6abb2f73 flags:# bot:InputUser url:string theme_params:flags.0?DataJSON = SimpleWebViewResult; messages.sendWebViewData#dc0242c8 bot:InputUser random_id:long button_text:string data:string = Updates; +
Simple webapps can only send back data to the bot through the MTProto API via a JS event.
Simple webapps can only be opened from a keyboardButtonSimpleWebView button contained in a reply keyboard identified by a replyKeyboardMarkup constructor.
To open them, users should call messages.requestSimpleWebView, and then open a webview using the url
contained in the returned simpleWebViewResultUrl.
Upon receiving a web_app_data_send
JS event from the web app, clients should invoke messages.sendWebViewData, passing the following arguments:
Normal webapps work similarly to inline bots »: they send messages on behalf of the user to the chat from which the query originated.
Normal webapps can be opened from:
To open them, clients should first ask permission should call messages.requestWebView, and then open a webview using the url
contained in the returned webViewResultUrl.
After loading the webview, until it is closed, the user client must invoke messages.prolongWebView every 60 seconds.
diff --git a/data/web/corefork.telegram.org/constructor/inlineKeyboardMarkup.html b/data/web/corefork.telegram.org/constructor/inlineKeyboardMarkup.html deleted file mode 100644 index 6b1b40cd8e..0000000000 --- a/data/web/corefork.telegram.org/constructor/inlineKeyboardMarkup.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - -