aboutsummaryrefslogtreecommitdiff
path: root/files/ru/web/api/windoworworkerglobalscope/settimeout/index.html
diff options
context:
space:
mode:
authorPeter Bengtsson <mail@peterbe.com>2021-07-27 15:17:31 -0400
committerGitHub <noreply@github.com>2021-07-27 22:17:31 +0300
commit7a2cfc4872ec27ef4ea5aa79f01dcb03a9a24d88 (patch)
tree520bd15be92236f2e90ab4b66389759ebc09f54f /files/ru/web/api/windoworworkerglobalscope/settimeout/index.html
parent20c7fd773df964681f7dd9d7a305293abd5a04ad (diff)
downloadtranslated-content-7a2cfc4872ec27ef4ea5aa79f01dcb03a9a24d88.tar.gz
translated-content-7a2cfc4872ec27ef4ea5aa79f01dcb03a9a24d88.tar.bz2
translated-content-7a2cfc4872ec27ef4ea5aa79f01dcb03a9a24d88.zip
remove link 'title' attributes that's just the 'href' (ru, part 4) (#1748)
Diffstat (limited to 'files/ru/web/api/windoworworkerglobalscope/settimeout/index.html')
-rw-r--r--files/ru/web/api/windoworworkerglobalscope/settimeout/index.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/files/ru/web/api/windoworworkerglobalscope/settimeout/index.html b/files/ru/web/api/windoworworkerglobalscope/settimeout/index.html
index d8c826dd5c..dbc08996a2 100644
--- a/files/ru/web/api/windoworworkerglobalscope/settimeout/index.html
+++ b/files/ru/web/api/windoworworkerglobalscope/settimeout/index.html
@@ -228,19 +228,19 @@ window.setTimeout("alert(\"Hello World!\");", 500);
<h3 id="Минимальная_максимальная_задержка_и_вложенность_таймаута"><span class="VIiyi" lang="ru"><span class="ChMk0b JLqJ4b"><span>Минимальная/ максимальная задержка и вложенность таймаута</span></span></span></h3>
-<p><a class="external" href="http://code.google.com/p/chromium/issues/detail?id=792#c10" title="http://code.google.com/p/chromium/issues/detail?id=792#c10">Historically</a> browsers implement <code>setTimeout()</code> "clamping": successive <code>setTimeout()</code> calls with <code>delay</code> smaller than the "minimum delay" limit are forced to use at least the minimum delay. The minimum delay, <code>DOM_MIN_TIMEOUT_VALUE</code>, is 4 ms (stored in a preference in Firefox: <code>dom.min_timeout_value</code>), with a <code>DOM_CLAMP_TIMEOUT_NESTING_LEVEL</code> of 5ms.</p>
+<p><a class="external" href="http://code.google.com/p/chromium/issues/detail?id=792#c10">Historically</a> browsers implement <code>setTimeout()</code> "clamping": successive <code>setTimeout()</code> calls with <code>delay</code> smaller than the "minimum delay" limit are forced to use at least the minimum delay. The minimum delay, <code>DOM_MIN_TIMEOUT_VALUE</code>, is 4 ms (stored in a preference in Firefox: <code>dom.min_timeout_value</code>), with a <code>DOM_CLAMP_TIMEOUT_NESTING_LEVEL</code> of 5ms.</p>
<p>In fact, 4ms is <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/timers.html#timers">specified by the HTML5 spec</a> and is consistent across browsers released in 2010 and onward. Prior to {{ geckoRelease("5.0") }}, the minimum timeout value for nested timeouts was 10 ms.</p>
<p>In addition to "clamping", the timeout can also fire later when the page (or the OS/browser itself) is busy with other tasks.</p>
-<p>To implement a 0 ms timeout in a modern browser, you can use {{ domxref("window.postMessage()") }} as <a class="external" href="http://dbaron.org/log/20100309-faster-timeouts" title="http://dbaron.org/log/20100309-faster-timeouts">described here</a>.</p>
+<p>To implement a 0 ms timeout in a modern browser, you can use {{ domxref("window.postMessage()") }} as <a class="external" href="http://dbaron.org/log/20100309-faster-timeouts">described here</a>.</p>
<p>Browsers including Internet Explorer, Chrome, Safari, and Firefox store the delay as a 32-bit signed Integer internally. This causes an Integer overflow when using delays larger than 2147483647, resulting in the timeout being executed immediately.</p>
<h4 id="Неактивные_вкладки">Неактивные вкладки</h4>
-<p>In {{ geckoRelease("5.0") }} and Chrome 11, timeouts are clamped to firing no more often than once per second (1000ms) in inactive tabs; see {{ bug(633421) }} for more information about this in Mozilla or <a class="external" href="http://crbug.com/66078" title="http://crbug.com/66078">crbug.com/66078</a> for details about this in Chrome.</p>
+<p>In {{ geckoRelease("5.0") }} and Chrome 11, timeouts are clamped to firing no more often than once per second (1000ms) in inactive tabs; see {{ bug(633421) }} for more information about this in Mozilla or <a class="external" href="http://crbug.com/66078">crbug.com/66078</a> for details about this in Chrome.</p>
<h2 id="Совместимость_с_браузерами">Совместимость с браузерами</h2>
@@ -248,7 +248,7 @@ window.setTimeout("alert(\"Hello World!\");", 500);
<h2 id="Specification" name="Specification">Спецификация</h2>
-<p>Part of DOM level 0, as specified in <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#timers" title="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#timers">HTML5</a>.</p>
+<p>Part of DOM level 0, as specified in <a class="external" href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#timers">HTML5</a>.</p>
<h2 id="See_also" name="See_also">Также интересно</h2>