diff options
Diffstat (limited to 'files/ja/web/api/page_visibility_api/index.html')
| -rw-r--r-- | files/ja/web/api/page_visibility_api/index.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/files/ja/web/api/page_visibility_api/index.html b/files/ja/web/api/page_visibility_api/index.html index ca03415e4d..d290675ee3 100644 --- a/files/ja/web/api/page_visibility_api/index.html +++ b/files/ja/web/api/page_visibility_api/index.html @@ -43,11 +43,11 @@ original_slug: Web/Guide/User_experience/Using_the_Page_Visibility_API <ul> <li>Most browsers stop sending {{domxref("Window.requestAnimationFrame", "requestAnimationFrame()")}} callbacks to background tabs or hidden {{ HTMLElement("iframe") }}s in order to improve performance and battery life.</li> - <li>Timers such as {{domxref("WindowOrWorkerGlobalScope.setTimeout", "setTimeout()")}} are throttled in background/inactive tabs to help improve performance. See <a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout#Reasons_for_delays_longer_than_specified">Reasons for delays longer than specified</a> for more details.</li> + <li>Timers such as {{domxref("WindowOrWorkerGlobalScope.setTimeout", "setTimeout()")}} are throttled in background/inactive tabs to help improve performance. See <a href="/ja/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout#Reasons_for_delays_longer_than_specified">Reasons for delays longer than specified</a> for more details.</li> <li>Budget-based background timeout throttling is now available in modern browsers (Firefox 58+, Chrome 57+), placing an additional limit on background timer CPU usage. This operates in a similar way across modern browsers, with the details being as follows: <ul> <li>In Firefox, windows in background tabs each have their own time budget in milliseconds — a max and a min value of +50 ms and -150 ms, respectively. Chrome is very similar except that the budget is specified in seconds.</li> - <li>Windows are subjected to throttling after 30 seconds, with the same throttling delay rules as specified for window timers (again, see <a href="/en-US/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout#Reasons_for_delays_longer_than_specified">Reasons for delays longer than specified</a>). In Chrome, this value is 10 seconds.</li> + <li>Windows are subjected to throttling after 30 seconds, with the same throttling delay rules as specified for window timers (again, see <a href="/ja/docs/Web/API/WindowOrWorkerGlobalScope/setTimeout#Reasons_for_delays_longer_than_specified">Reasons for delays longer than specified</a>). In Chrome, this value is 10 seconds.</li> <li>Timer tasks are only permitted when the budget is non-negative.</li> <li>Once a timer's code has finished running, the duration of time it took to execute is subtracted from its window's timeout budget.</li> <li>The budget regenerates at a rate of 10 ms per second, in both Firefox and Chrome.</li> @@ -59,8 +59,8 @@ original_slug: Web/Guide/User_experience/Using_the_Page_Visibility_API <ul> <li>Tabs which are playing audio are considered foreground and aren’t throttled.</li> - <li>Tabs running code that's using real-time network connections (<a href="/en-US/docs/Web/API/WebSockets_API">WebSockets</a> and <a href="/en-US/docs/Web/API/WebRTC_API">WebRTC</a>) go unthrottled in order to avoid closing these connections timing out and getting unexpectedly closed.</li> - <li><a href="/en-US/docs/Web/API/IndexedDB_API">IndexedDB</a> processes are also left unthrottled in order to avoid timeouts.</li> + <li>Tabs running code that's using real-time network connections (<a href="/ja/docs/Web/API/WebSockets_API">WebSockets</a> and <a href="/ja/docs/Web/API/WebRTC_API">WebRTC</a>) go unthrottled in order to avoid closing these connections timing out and getting unexpectedly closed.</li> + <li><a href="/ja/docs/Web/API/IndexedDB_API">IndexedDB</a> processes are also left unthrottled in order to avoid timeouts.</li> </ul> <h2 id="Example" name="Example">例</h2> |