Index: third_party/WebKit/LayoutTests/external/wpt/keyboard-lock/idlharness.https.html |
diff --git a/third_party/WebKit/LayoutTests/external/wpt/keyboard-lock/idlharness.https.html b/third_party/WebKit/LayoutTests/external/wpt/keyboard-lock/idlharness.https.html |
index 40b6a8af5cb05f00e370cf30f6dcbf64fad5c308..6fabb4117436570586032c7b20f9423e9d0a8276 100644 |
--- a/third_party/WebKit/LayoutTests/external/wpt/keyboard-lock/idlharness.https.html |
+++ b/third_party/WebKit/LayoutTests/external/wpt/keyboard-lock/idlharness.https.html |
@@ -14,7 +14,7 @@ interface Navigator { |
}; |
</pre> |
<!-- |
- The reason of the failure of requestKeyLock test looks like a code defect in |
+ The reason of the failure of requestKeyboardLock test looks like a code defect in |
idlharness.js. media-capabilities/idlharness.html is also impacted by this |
issue. See https://codereview.chromium.org/2805763004/#ps620001, which |
includes a potential fix. |
@@ -22,8 +22,8 @@ interface Navigator { |
--> |
<pre id="idl" style="display: none"> |
partial interface Navigator { |
- [SecureContext] Promise<void> requestKeyLock(optional sequence<DOMString> keyCodes = []); |
- [SecureContext] void cancelKeyLock(); |
+ [SecureContext] Promise<void> requestKeyboardLock(optional sequence<DOMString> keyCodes = []); |
+ [SecureContext] void cancelKeyboardLock(); |
}; |
</pre> |
<script> |