mirror of
https://github.com/MarshalX/telegram-crawler.git
synced 2024-12-28 23:38:26 +01:00
Update content of files
This commit is contained in:
parent
581a0cb2bc
commit
6ad1faa596
2 changed files with 10 additions and 2 deletions
|
@ -154,7 +154,13 @@
|
|||
<p>Bot web apps can be themed according to the following theme parameters, passed as a JSON object to the <code>theme_params</code> parameter of the <a href="/method/messages.requestSimpleWebView">messages.requestSimpleWebView</a> and <a href="/method/messages.requestWebView">messages.requestWebView</a> methods. </p>
|
||||
<p>This JSON object has the the following keys, containing color theme information (hex string, RGB, no alpha) to pass to the web app:</p>
|
||||
<ul>
|
||||
<li><code>bg_color</code> - Background color <br><em> <code>secondary_bg_color</code> - Secondary background color <br></em> <code>text_color</code> - Text color <br><em> <code>hint_color</code> - Hint text color <br></em> <code>link_color</code> - Link color <br><em> <code>button_color</code> - Button color <br></em> <code>button_text_color</code> - Button text color</li>
|
||||
<li><code>bg_color</code> - Background color</li>
|
||||
<li><code>secondary_bg_color</code> - Secondary background color</li>
|
||||
<li><code>text_color</code> - Text color</li>
|
||||
<li><code>hint_color</code> - Hint text color</li>
|
||||
<li><code>link_color</code> - Link color</li>
|
||||
<li><code>button_color</code> - Button color</li>
|
||||
<li><code>button_text_color</code> - Button text color</li>
|
||||
</ul></div>
|
||||
|
||||
</div>
|
||||
|
|
|
@ -147,7 +147,7 @@ The web app must also be expanded when the user swipes up on the webview. </p>
|
|||
<p>This event must be ignored <em>during</em> a user swipe down, used to reduce the webview.</p>
|
||||
<h4><a class="anchor" href="#web-app-request-viewport" id="web-app-request-viewport" name="web-app-request-viewport"><i class="anchor-icon"></i></a><code>web_app_request_viewport</code></h4>
|
||||
<p>No event payload.</p>
|
||||
<p>Used by web apps to request information about the viewport, clients should emit a <a href="/api/bots/webapps#viewport-changed">viewport_changed event</a></p>
|
||||
<p>Used by web apps to request information about the viewport, clients should emit a <a href="/api/bots/webapps#viewport-changed">viewport_changed event</a>.</p>
|
||||
<h4><a class="anchor" href="#web-app-request-theme" id="web-app-request-theme" name="web-app-request-theme"><i class="anchor-icon"></i></a><code>web_app_request_theme</code></h4>
|
||||
<p>No event payload.</p>
|
||||
<p>Used by web apps to request information about the current theme, clients should emit a <a href="/api/bots/webapps#theme-changed">theme_changed event</a>.</p>
|
||||
|
@ -166,6 +166,8 @@ The web app must also be expanded when the user swipes up on the webview. </p>
|
|||
<li><code>is_progress_visible</code> - Indicates whether the button should display a loading indicator (boolean, false by default)</li>
|
||||
</ul>
|
||||
<p>Configures the main button, located immediately below the webview: when the user presses it a <a href="/api/bots/webapps#main-button-pressed"><code>main_button_pressed</code> event should be emitted by the client</a>. </p>
|
||||
<p>Note that if <code>is_visible</code> is true, <em>only when opening web apps from the <a href="/api/bots/attach">attachment menu</a></em> and <em>only on clients with tab bars</em>, the main button should be displayed only after the first user tap inside of the webview (to prevent bots from immediately blocking the tab bar).<br>
|
||||
Otherwise, the main button can be displayed right away if <code>is_visible</code> is true. </p>
|
||||
<h4><a class="anchor" href="#web-app-setup-back-button" id="web-app-setup-back-button" name="web-app-setup-back-button"><i class="anchor-icon"></i></a><code>web_app_setup_back_button</code></h4>
|
||||
<p>Event data: a JSON object with an <code>is_visible</code> boolean field.</p>
|
||||
<p>Determines whether to show or hide the back button: when the user presses it a <a href="/api/bots/webapps#back-button-pressed"><code>back_button_pressed</code> event should be emitted by the client</a>.<br>
|
||||
|
|
Loading…
Reference in a new issue