From 2da1ec700bc191256e21037a0f09d7d8f7b0a7cc Mon Sep 17 00:00:00 2001 From: A1lo Date: Thu, 20 Apr 2023 03:53:16 +0800 Subject: [PATCH] chore(ru): remove `WebkitBug` macro (#12834) --- files/ru/web/api/selection/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/ru/web/api/selection/index.md b/files/ru/web/api/selection/index.md index 1c451ac7383afd..0278ece5d7ca21 100644 --- a/files/ru/web/api/selection/index.md +++ b/files/ru/web/api/selection/index.md @@ -98,7 +98,7 @@ As the [Selection API specification notes](https://www.w3.org/TR/selection-api/# Selection and input focus (indicated by {{DOMxRef("Document.activeElement")}}) have a complex relationship that varies by browser. In cross-browser compatible code, it's better to handle them separately. -Safari and Chrome (unlike Firefox) currently focus the element containing selection when modifying the selection programmatically; it's possible that this may change in the future (see [W3C bug 14383](https://www.w3.org/Bugs/Public/show_bug.cgi?id=14383) and {{WebKitBug("38696")}}). +Safari and Chrome (unlike Firefox) currently focus the element containing selection when modifying the selection programmatically; it's possible that this may change in the future (see [W3C bug 14383](https://www.w3.org/Bugs/Public/show_bug.cgi?id=14383) and [WebKit bug 38696](https://webkit.org/b/38696)). ### Behavior of Selection API in terms of editing host focus changes