Document background processing limitations in Exporting for the Web

(cherry picked from commit 482e0c6544)
This commit is contained in:
Hugo Locurcio
2021-12-13 01:17:43 +01:00
committed by Rémi Verschelde
parent 857599e6b9
commit 61c5bf2698

View File

@@ -110,6 +110,19 @@ The method ``OS.is_userfs_persistent()`` can be used to check if the
``user://`` file system is persistent, but can give false positives in some
cases.
Background processing
~~~~~~~~~~~~~~~~~~~~~
The project will be paused by the browser when the tab is no longer the active
tab in the user's browser. This means functions such as ``_process()`` and
``_physics_process()`` will no longer run until the tab is made active again by
the user (by switching back to the tab). This can cause networked games to
disconnect if the user switches tabs for a long duration.
This limitation does not apply to unfocused browser *windows*. Therefore, on the
user's side, this can be worked around by running the project in a separate
*window* instead of a separate tab.
Threads
~~~~~~~
@@ -118,7 +131,7 @@ only available if the appropriate **Export Type** is set and support for it
across browsers is still limited.
.. warning:: Requires a :ref:`secure context <doc_javascript_secure_contexts>`.
Browsers are also starting to require that the web page is served with specific
Browsers also require that the web page is served with specific
`cross-origin isolation headers <https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy>`__.
GDNative