diff options
Diffstat (limited to 'files/ru/web/api/fullscreen_api/index.html')
| -rw-r--r-- | files/ru/web/api/fullscreen_api/index.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/files/ru/web/api/fullscreen_api/index.html b/files/ru/web/api/fullscreen_api/index.html index f0cc07a8cf..96742191eb 100644 --- a/files/ru/web/api/fullscreen_api/index.html +++ b/files/ru/web/api/fullscreen_api/index.html @@ -82,7 +82,7 @@ original_slug: DOM/Using_fullscreen_mode </dd> </dl> -<h2 id="Events" name="Events">Events</h2> +<h2 id="Events">Events</h2> <p><em>The Fullscreen API defines two events which can be used to detect when full-screen mode is turned on and off, as well as when errors occur during the process of changing between full-screen and windowed modes.</em></p> @@ -106,7 +106,7 @@ original_slug: DOM/Using_fullscreen_mode <p>See <a href="/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy">Using Feature Policy</a> to learn more about using Feature Policy to control access to an API.</p> -<h2 id="Usage_notes" name="Usage_notes">Usage notes</h2> +<h2 id="Usage_notes">Usage notes</h2> <p>Users can choose to exit full-screen mode simply by pressing the <kbd>ESC</kbd> (or <kbd>F11</kbd>) key, rather than waiting for the site or app to programmatically do so. Make sure you provide, somewhere in your user interface, appropriate user interface elements that inform the user that this option is available to them.</p> @@ -168,7 +168,7 @@ original_slug: DOM/Using_fullscreen_mode </tbody> </table> -<h2 id="Browser_compatibility" name="Browser_compatibility">Browser compatibility</h2> +<h2 id="Browser_compatibility">Browser compatibility</h2> <h3 id="Document.fullscreen"><code>Document.fullscreen</code></h3> |